Dynamic functional testing coverage based on failure dependency graph

• US 8,132,056 B2
• Filed: 02/28/2008
• Issued: 03/06/2012
• Est. Priority Date: 02/28/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Thakkar, Rajesh P., Kurian, John
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): Leibovich, Yair
• Application Number:
  US12/039,190
• Publication Number:
  US 20090222697A1
• Time in Patent Office: 1,468 Days
• Field of Search: 714/38, 714/25, 714/27, 714/38.1
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/3676 for coverage analysis

Abstract

A method, system and computer program product is disclosed for providing test coverage for detecting failures in a software application. The method comprises the steps of identifying a set of test cases; and for each of at least a subset of said test cases, identifying one or more of the other test cases that depend on said each of the test cases based on a defined functional relationship. The method comprises the further steps of using a selected one of said subset of test cases to test the software application; and when said test of the software application fails, then testing the software application with the one or more of the other test cases that depend on said selected one of the test cases based on said functional relationship.

Claims

1. A method of providing test coverage for detecting failures in a software application, the method comprising the steps of:

identifying a set of test cases;

for each of at least a subset of said test cases, identifying one or more of the other test cases that depend on said each of the test cases based on a defined functional relationship, including recording each test case in the form of a shared object map;

using a selected one of said subset of test cases to test the software application; and

when said test of the software application fails, then testing the software application with the one or more of the other test cases that depends on said selected one of the test cases based on said functional relationship, including using said shared object map to identify said one or more of the other test cases.

2. A method according to claim 1, wherein the step of identifying one or more of the other test cases that depends on said each of said subset of the test cases includes the step of, for each of the at least one of the subset of test cases, building a dependency graph, starting from said at least one of the test cases, based on said functional relationship, and wherein each of said one or more of the other test cases forms a respective one node on said dependency graph.

3. A method according to claim 2, wherein the step of testing the software application includes the step of traversing the dependency graph that starts from the selected test case to identify said one or more other test cases that depend from said selected test case.

4. A method according to claim 3, wherein the step of testing said software application further includes the step of testing the software application with all of the test cases on the dependency graph that starts from the selected test case.

5. A method according to claim 1, wherein:

each of the set of test cases is associated with one or more objects; and

said defined functional relationship is based on said objects.

6. A method according to claim 5, wherein:

the test cases share the objects; and

identifying one or more of the other test cases that share objects with said each test case.

7. A method according to claim 6, further includes the step of extracting dependencies among the test cases from said objects.

8. A method according to claim 1, wherein the step of identifying one or more of the other test cases includes the step of mining information about functional relationships between the set of test cases to extract said defined relationship.

9. A method of providing test coverage for detecting failures in a software application, the method comprising the steps of:

identifying a set of test cases;

for each of at least a subset of said test cases, identifying one or more of the other test cases that depend on said each of the test cases based on a defined functional relationship;

using a selected one of said subset of test cases to test the software application; and

when said test of the software application fails, then testing the software application with the one or more of the other test cases that depends on said selected one of the test cases based on said functional relationship; and

wherein

the step of identifying one or more of the other test cases includes the step of mining information about functional relationships between the set of test cases to extract said defined relationship; and

the mining step includes the step of recording each test case in the form of a script and a shared object map.

10. A method according to claim 9, wherein failures of test cases lead to dynamic coverage of additional cases that are related to the failed test case based on functional and failure dependencies among the test cases.

11. A system for providing test coverage for detecting failures in a software application, the system comprising:

one or more processing units configured for;

identifying, for each of at least a subset of test cases formed from a set of test cases, one or more of the other test cases that depend on said each of the test cases based on a defined functional relationship, including recording each test case in the form of a shared object map;

using a selected one of said subset of test cases to test the software application; and

when said test of the software application fails, then testing the software application with the one or more of the other test cases that depend on said selected one of the test cases based on said functional relationship, including using said shared object map to identify said one or more of the other test cases.

12. A system according to claim 11, wherein the one or more of the processing units are further configured for building a dependency graph for each of the at least one of the subset of test cases, and starting from said at least one of the test cases, based on said functional relationship, and wherein each of said one or more of the other test cases forms a respective one node on said dependency graph.

13. A system according to claim 12, wherein the one or more processing units are configured for traversing the dependency graph that starts from the selected test case to identify said one or more other test cases that depend from said selected test case.

14. A system according to claim 11, wherein:

each of the set of test cases is associated with one or more objects;

the test cases share the objects; and

said defined functional relationship is based on which of the other test cases share objects with said each test case.

15. A system according to claim 14, wherein failures of test cases lead to dynamic coverage of additional cases that are related to the failed test case based on functional and failure dependencies among the test cases.

16. A computer readable storage media, tangibly embodying a program of instructions executable by the computer to perform method steps for providing test coverage for detecting failures in a software application, said method steps comprising:

for each of at least a subset of test cases formed from a set of test cases, identifying one or more of the other test cases that depend on said each of the test cases based on a defined functional relationship, including recording each test case in the form of a shared object map;

using a selected one of said subset of test cases to test the software application; and

when said test of the software application fails, then testing the software application with the one or more of the other test cases that depend on said selected one of the test cases based on said functional relationship, including using said shared object map to identify said one or more of the other test cases.

17. A computer readable storage media according to claim 16, wherein the step of identifying one or more of the other test cases includes the step of building a dependency graph for each of the at least one of the subset of test cases, starting from said at least one of the test cases, based on said functional relationship, and wherein each of said one or more of the other test cases forms a respective one node on said dependency graph.

18. A computer readable storage media according to claim 17, wherein the step of identifying said one or more of the other test cases includes the step of traversing the dependency graph that starts from the selected test case to identify said one or more other test cases that depend from said selected test case.

19. A computer readable storage media according to claim 16, wherein:

each of the group of test cases is associated with one or more objects;

the test cases share the objects; and

said defined functional relationship is based on which of the other test cases share objects with said each test case.

20. A computer readable storage media according to claim 19, wherein failures of test cases lead to dynamic coverage of additional cases that are related to the failed test case based on functional and failure dependencies among the test cases.