ASSOCIATION BETWEEN A TEST CASE AND SOURCE CODE

• US 20180046569A1
• Filed: 08/09/2016
• Published: 02/15/2018
• Est. Priority Date: 08/09/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hisagi, Sakura B., Unno, Asuka, Watanabe, Terue
• Granted Patent: US 10,169,210 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 11/3672 Test management

Abstract

The present invention may be a method, a system, and/or a computer program product. An embodiment of the present invention provides a computer-implemented method for associating one or more test cases with one or more source code parts for a test target, or vice versa. The method comprises the followings: obtaining one or more historical data in which one or more modification histories made in one or more source codes are associated with one or more test operation histories made in the test target after the one or more modifications; for each of the historical data, determining whether the test operation history has one or more parts which are identical or similar with those in one or more test cases; and if the determination is positive, associating the one or more test cases with one or more source code parts in the one or more modification histories which have been associated with the test operation history, or vice versa.

Claims

1. A computer-implemented method for associating one or more test cases with one or more source code parts for a test target comprising:

obtaining historical data comprising one or more modification histories and one or more associated test operation histories, wherein a modification history comprises one or more modifications made in one or more source code parts, and a test operation history comprises one or more test processing parts corresponding to one or more test operations conducted on a test target after the one or more modifications;

for each of the historical data, determining whether a test operation history has one or more test processing parts which are identical or similar to test processing parts in one or more test cases; and

associating the one or more test cases with one or more source code parts in one or more modification histories which have been associated with the test operation history responsive to determining that the test operation history has one or more test processing parts which are identical or similar to test processing parts in one or more test cases.

2. The method according to claim 1, wherein an association between the one or more modification histories and the one or more test operation histories is determined by finding, from one or more user operation histories made in a time sequence order, a set of one or more source code modifications and one or more test operations and generating historical data for the set.

3. The method according to claim 1, wherein an association between the one or more test cases and one or more source code parts is determined by associating the one or more test cases with the test operation history in the historical data.

4. The method according to claim 1, wherein at least one of the one or more test cases is one which has been prepared by deleting, from an original test case which comprises one or more operation parts, one or more data parts and one or more verification parts, the one or more verification parts.

5. The method according to claim 1, wherein the test case is one which has been prepared by deleting, from an original test case which comprises one or more test processing parts, a pre-processing part which is carried out before the one or more test processing parts are carried out and a post-processing part which is carried out after the one or more test processing parts are carried out.

6. The method according to claim 1, wherein the test case comprises one or more operation parts, one or more data parts and one or more graphical user interface component IDs.

7. The method according to claim 1, wherein the test operation history comprises one or more operation parts, one or more data parts and one or more graphical user interface component IDs.

8. The method according to claim 1, wherein the determination is carried out using a sequential pattern mining.

9. The method according to claim 1, wherein the determination is carried out by comparing a whole or part of the test operation history with a whole or part of each of the one or more test cases.

10. The method according to claim 1, wherein a test operation is carried out on a graphical user interface.

11. The method according to claim 1, further comprising assigning a degree of reliability to each of the plurality of associations between the one or more test cases and the one or more source code parts.

12. The method according to claim 11, further comprising assigning a lower degree of reliability to each of a plurality of associations corresponding to a plurality of test cases for which no verification parts are present.

13. The method according to claim 11, further comprising assigning a higher degree of reliability to each of the plurality of associations corresponding to a plurality of test cases for which verification parts are present.

14. The method according to claim 11, wherein the degree of reliability of an association is inversely correlated to number of modification histories corresponding to the association.

15. The method according to claim 11, wherein the degree of reliability of an association is directly correlated to an amount of time elapsed since an earliest operation in a modification history corresponding to the association was carried out.

16. The method according to claim 11, wherein the degree of reliability of an association is directly correlated to an amount of time elapsed since an earliest operation in the test operation history was carried out.

17. The method according to claim 11, wherein the degree of reliability of an association is directly correlated to an amount of time elapsed since a corresponding test operation history was generated.

18. The method according to claim 11, wherein the degree of reliability of an association is inversely correlated to a number of modification histories corresponding to the test operation history corresponding to the association.

19-20. -20. (canceled)