Software test management program software test management apparatus and software test management method

• US 20070174711A1
• Filed: 02/14/2006
• Published: 07/26/2007
• Est. Priority Date: 11/14/2005
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Yamamoto, Rieko, Uehara, Tadahiro, Kodaka, Toshihiro, Katayama, Asako, Ohashi, Kyoko
• Granted Patent: US 7,882,493 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3672 Test management

Abstract

A software test management program, a software test management apparatus and a software test management method can integrally manage test-related information that are to be effectively exploited among test support functions. The software test management apparatus includes a design model registration section 31 that registers a design model, a source code registration section 34 that registers a source code, a test model registration section 32 that registers the test model prepared to correspond to the design model and also the corresponding relationship between the design model and the test model, an execution trace registration section 33 that registers the execution trace of each test case obtained by executing the source code according to the test cases in the test model, the corresponding relationship between the test model and the execution trace and also the corresponding relationship between the execution trace and the source code and a model relations management interface 12 that traces all the corresponding relationships.

Claims

1. A software test management program for causing a computer to manage information relating to a software test, the program comprising:

a design model registration step that registers a design model including use cases;

a source code registration step that registers a source code prepared on the basis of the design model;

a test model registration step that registers the test cases prepared to correspond to the use cases in the design model and test data as test model and also the corresponding relationship between the design model and the test model;

an execution trace registration step that registers the execution trace of each test case obtained by executing the source code according to the test cases in the test model, the corresponding relationship between the test model and the execution trace and also the corresponding relationship between the execution trace and the source code; and

a model relations management step that traces the corresponding relationship among the design model, the test model, the execution trace and the source code on the basis of the corresponding relationship between the design model and the test model, the corresponding relationship between the test model and the execution trace and the corresponding relationship between the execution trace and the source code.

2. The program according to claim 1, further comprising:

an influential test case identifying step that identifies the altered part of the altered source code, detects the execution trace including the altered part, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing in the model relationship management step and, if the element of the design model includes an alteration, outputs the test case as amendment-requiring test case after the model relations management step.

3. The program according to claim 1, further comprising:

an unextracted test case generation step that detects the unexecuted part of the source code as unexecuted block by comparing the corresponding positions of all the execution trace and the source code on the basis of the tracing in the model relations management step, detects the conditional sentence that determines not to execute the unexecuted block of the source code, detects the execution trace that the conditional sentence is executed and the test case corresponding the execution trace on the basis of the tracing in the model relations management step, determines the condition for the unexecuted block to be executed by analyzing the conditional sentence and outputs the test case and the condition as reference information for the test case to be newly prepared after the model relations management step.

4. The program according to claim 1, further comprising:

a corresponding source code identifying step that detects the test case corresponding to the element specified in the design model, the execution trace corresponding to the test case and the source code corresponding to the execution trace on the basis of the tracing in the model relations management step and outputs the source code after the model relations management step.

5. The program according to claim 1, further comprising:

a corresponding design model identifying step that detects the execution trace that the specified element in the source code is executed, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing in the model relations management step and outputs the element of the design model after the model relations management step.

6. The program according to claim 3, wherein

the unextracted test case generation step further outputs the element of the design model corresponding to the test case as information for preparing a new test case.

7. A software test management apparatus for managing information relating to a software test, the apparatus comprising:

a design model registration section that registers a design model including use cases;

a source code registration section that registers a source code prepared on the basis of the design model;

a test model registration section that registers the test cases prepared to correspond to the use cases in the design model and test data as test model and also the corresponding relationship between the design model and the test model;

an execution trace registration section that registers the execution trace of each test case obtained by executing the source code according to the test cases in the test model, the corresponding relationship between the test model and the execution trace and also the corresponding relationship between the execution trace and the source code; and

a model relations management section that traces the corresponding relationship among the design model, the test model, the execution trace and the source code on the basis of the corresponding relationship between the design model and the test model, the corresponding relationship between the test model and the execution trace and the corresponding relationship between the execution trace and the source code.

8. The apparatus according to claim 7, further comprising:

an influential test case identifying section that identifies the altered part of the altered source code, detects the execution trace including the altered part, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing by the model relationship management section and, if the element of the design model includes an alteration, outputs the test case as amendment-requiring test case.

9. The apparatus according to claim 7, further comprising:

an unextracted test case generation section that detects the unexecuted part of the source code as unexecuted block by comparing the corresponding positions of all the execution trace and the source code on the basis of the tracing by the model relations management section, detects the conditional sentence that determines not to execute the unexecuted block of the source code, detects the execution trace that the conditional sentence is executed and the test case corresponding the execution trace on the basis of the tracing by the model relations management section, determines the condition for the unexecuted block to be executed by analyzing the conditional sentence and outputs the test case and the condition as reference information for the test case to be newly prepared.

10. The apparatus according to claim 7, further comprising:

a corresponding source code identifying section that detects the test case corresponding to the element specified in the design model, the execution trace corresponding to the test case and the source code corresponding to the execution trace on the basis of the tracing by the model relations management section and outputs the source code.

11. The apparatus according to claim 7, further comprising:

a corresponding design model identifying section that detects the execution trace that the specified element in the source code is executed, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing by the model relations management section and outputs the element of the design model.

12. The apparatus according to claim 9, wherein

the unextracted test case generation section further outputs the element of the design model corresponding to the test case as information for generating a new test case.

13. A software test management method for managing information relating to a software test, the method comprising:

a design model registration step that registers a design model including use cases;

a source code registration step that registers a source code prepared on the basis of the design model;

a test model registration step that registers the test cases prepared to correspond to the use cases in the design model and test data as test model and also the corresponding relationship between the design model and the test model;

an execution trace registration step that registers the execution trace of each test case obtained by executing the source code according to the test cases in the test model, the corresponding relationship between the test model and the execution trace and also the corresponding relationship between the execution trace and the source code; and

a model relations management step that traces the corresponding relationship among the design model, the test model, the execution trace and the source code on the basis of the corresponding relationship between the design model and the test model, the corresponding relationship between the test model and the execution trace and the corresponding relationship between the execution trace and the source code.

14. The method according to claim 13, further comprising:

an influential test case identifying step that identifies the altered part of the altered source code, detects the execution trace including the altered part, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing in the model relationship management step and, if the element of the design model includes an alteration, outputs the test case as amendment-requiring test case after the model relations management step.

15. The method according to claim 13, further comprising:

an unextracted test case generation step that detects the unexecuted part of the source code as unexecuted block by comparing the corresponding positions of all the execution trace and the source code on the basis of the tracing in the model relations management step, detects the conditional sentence that determines not to execute the unexecuted block of the source code, detects the execution trace that the conditional sentence is executed and the test case corresponding the execution trace on the basis of the tracing in the model relations management step, determines the condition for the unexecuted block to be executed by analyzing the conditional sentence and outputs the test case and the condition as reference information for the test case to be newly prepared after the model relations management step.

16. The method according to claim 13, further comprising:

a corresponding source code identifying step that detects the test case corresponding to the element specified in the design model, the execution trace corresponding to the test case and the source code corresponding to the execution trace on the basis of the tracing in the model relations management step and outputs the source code after the model relations management step.

17. The method according to claim 13, further comprising:

a corresponding design model identifying step that detects the execution trace that the specified element in the source code is executed, the test case corresponding to the execution trace and the element of the design model corresponding to the test case on the basis of the tracing in the model relations management step and outputs the element of the design model after the model relations management step.

18. The method according to claim 15, wherein

the unextracted test case generation step further outputs the element of the design model corresponding to the test case as information for generating a new test case.