Browse Prior Art Database

Automated creation of Test Cases from reported Problems & Creation of Test Cases for the new Product from Predicted Problems

IP.com Disclosure Number: IPCOM000131992D
Original Publication Date: 2005-Nov-28
Included in the Prior Art Database: 2005-Nov-28
Document File: 5 page(s) / 37K

Publishing Venue

IBM

Abstract

Disclosed is a system which covers two parts, Automatic creation of Test Cases from reported Software Problem & Creation of Test Cases for the new Product from the Predicted Problems. Problem 1 in Present scenario ? It?s very difficult to cover all the features of a Software Product with all permutations & combinations in Test Cases. There are lots of problems are found during different test execution cycles for which Test Cases are not available. If the reported Problems are more, then it?s very difficult to maintain test cases for each problem. There is a duplication of task as create to Problem (SPR-Software Problem report) first & then also create Test Case for each problem. Solution for the Problem 1: Test Cases are always created in TCDB (Test Case Database) & Problems are always created in SPR (Software Problem Report) Database. Usually Software tester?s finds lots of problems during different Test execution cycles for which there is no Test Case available in TCDB. So after creating Problem in SPR Database our solution is providing a provision ?Create Test Case? (button) in SPR Database (where the Problem created) which will take Problem (SPR) fields & create a Test Case automatically. Problem 2 in Present scenario ? Testing team needs to create new Test Cases based on the features of the product. It?s difficult to predict what problem will occur for all the features. There are several features which are similar in different Software products. It is possible to predict all the possible problems which can occur in new product for the features which are similar to the features of already developed & tested software products. Presently there is no provision of creating Test Cases in TCDB by prediction of Problem which occurred in some other Software Products for similar features. Solution for the Problem 2: There are large numbers of Software products which are having similar features. If a new product is under development which will contain similar features of already developed & tested products. There are lots of problems reported for each feature in all products. So mapping features with the problems, all the problems which are reported for the feature which is matching with the feature of new product can be imported as predicted problems for the new product.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 45% of the total text.

Page 1 of 5

Automated creation of Test Cases from reported Problems & Creation of Test Cases for the new Product from Predicted Problems

Disclosed is a system which covers two parts, Automatic creation of Test Cases from reported Software Problem & Creation of Test Cases for the new Product from the Predicted Problems.

Brief Description of Automatic creation of Test Cases from reported Software Problem

Software product has several features. All these features need to be tested properly with all the permutations & Combinations.

Test Cases are always created in TCDB (Test Case Database) & Problems are always created in SPR (Software Problem Report) Database.

Testing Process:

1. Create Test Cases based on Software feature in TCDB.
2.Tester executes each Test case by following the steps mentioned in the Test Case, Pass or Fail depending upon the execution result.
3. Create a Problem (SPR) in SPR Database for each failed Test Case.

It's very difficult to cover all the features with all permutations & combinations in Test Cases. So there are lots of problems are found during test execution & if the reported Problems are more, then it's very difficult to maintain test cases for each problem.

It's always required to have Test Cases for each failed area to get correct count or report on actual Pass /Failed/ Block Test Cases. There are lots of SPR's for which no Test Case is available. So its a duplication of task as tester first creates SPR (Problem report) then creates Test Case for each problem

Solution:

There should not be duplication of work. And if Tester creates 100-200 Problems (SPR's) then it's very difficult to find & recollect Problem (SPR) at the time of creating Test Cases.

Test Case should get created automatically after creating an SPR whenever required.

Following are the important fields in Test Case & Problem (SPR) Schema which are relevant for our solution. There can additional fields also depending on the design.

Schema of Test Case contains following fields:

Title, Brief Description, Function & Sub-function: (This is Feature field of the Product), Build, Platform, Database, Severity, Execution Steps

Schema of Problem (SPR) contains following fields:

Title, Environment, Brief Description, Steps to Reproduce:

Tester will create a new Problem (SPR) & Click on the 'Create Test Case' button which is available in the Problem (SPR) creation template as shown in the Figure.1

1

Page 2 of 5

Click on Create Test Case' button will create a new Test Case in TCDB Technically 'Create Test Case' Button fires a query which will take fields from SPR Schema like Title, Brief Description, Steps to Reproduce' into new Test Case Schema fields Test Case Title, Brief Description & Execution steps respectively.

Figure.1

Software Problem Report

Title.........................

Phase: How found: Build:
Platform: DB: Severity:

Brief Description.........

Steps to Reproduce

Test Case

Title.........................

Brief Description.........

Steps to Reproduce

Creat...