Browse Prior Art Database

A system to suggest regression test cases based on indirect change set and component references

IP.com Disclosure Number: IPCOM000227936D
Publication Date: 2013-May-29
Document File: 5 page(s) / 133K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system that uses relationships/dependencies between source code files, source code change sets in the source code files, changesets delivered to resolve defects, and defect associations to affected tests, to suggest which test cases can be run to exercise related areas of a software product in order to minimize regressions to a software product's quality.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 27% of the total text.

Page 01 of 5

A system to suggest regression test cases based on indirect change set and component references

The quality assurance (QA) phase is an important cycle in the software development process. QA ensures that no adverse changes have been made to existing functions that may not have been changed during the current development cycle . The QA phase can be time consuming and resource intensive; in some cases, wasteful in terms of

resources when performing regression tests for every function in the product , even though there have been no changes. Tracking the change sets and trying to determine

which test cases may have been indirectly affected by those changes is a daunting task.

Three methods are needed in order to improve the operation of the QA phase . First, a method is needed that allows testers to quickly identify the functions that may have been affected, but not explicitly modified, during the software development cycle and then select the functions on which regression tests must be performed . Second, a more effective method is needed for identifying which test cases need to be run as a result of the changes, direct or indirect, to referenced components. Third, a method is needed to identify which test cases to run, based on defects/test result links, where

related or dependent code paths are exercised, in order to gain valuable insight into

which test cases could be run to perform regression tests of the software .

Currently, developers/testers can identify the software fixes that go into a given build and see which test cases these defects affect via a traceability link between the two . Teams cannot currently identify which test cases are affected by code changes if a test case to defect traceability link does not exist. For instance, if the defect was written from a customer report or if the defect was written outside a test cycle , there may test cases to address the customer problem. There is no linkage, however, between the test case for that customer problem and other test cases for other functions that also reference one of the modules modified in the change set .

The solution is a system that uses relationships/dependencies between source code files, source code change sets in the source code files , change sets delivered to resolve defects, and defect associations to affected tests to suggest which test cases can be run to exercise related areas of a software product in order to minimize regressions to a software product's quality.

The core functions and novel contributions of the invention include :


• For a given change set, a method to provide a list of test cases that can be run to verify that software quality has not regressed after a change to the source code


• For a given component, a method provide a list of impacted testcases that may need to be changed based on new changes to a referenced component


• For a component that is referenced the first time , a method to suggest new test cases written for the r...