TRACKING OF CODE BASE AND DEFECT DIAGNOSTIC COUPLING WITH AUTOMATED TRIAGE

• US 20130047141A1
• Filed: 03/29/2012
• Published: 02/21/2013
• Est. Priority Date: 08/16/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Shann, Katherine M., Whitbourne, Matthew D., Would, Daniel E., Xu, Shanna
• Granted Patent: US 9,104,806 B2
• Time in Patent Office: Days
• US Class Current: 717/128
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/30 Creation or generation of source code

Abstract

In response to a test case error generated by execution of a test case against a code build, a source code segment that caused the test case error is identified by a defect monitor. The identified source code segment is linked to the test case that generated the test case error. The linked source code segment is monitored for code changes. A determination is made as to whether a test case re-execution criterion associated with the test case has been satisfied based upon a detected code change of the linked source code segment. An indication to re-execute the test case is generated in response to determining that the test case re-execution criterion associated with the test case has been satisfied.

Claims

1. A method, comprising:

identifying, via a defect monitor in response to a test case error generated by execution of a test case against a code build, a source code segment that caused the test case error;

linking the identified source code segment to the test case that generated the test case error;

monitoring the linked source code segment for code changes;

determining whether a test case re-execution criterion associated with the test case has been satisfied based upon a detected code change of the linked source code segment; and

generating an indication to re-execute the test case in response to determining that the test case re-execution criterion associated with the test case has been satisfied.

2. The method of claim 1, where identifying, via the defect monitor in response to the test case error generated by execution of the test case against the code build, the source code segment that caused the test case error comprises:

analyzing a stack trace associated with the test case error;

determining, via the stack trace analysis, an executed code module that caused the test case error;

identifying a source code module used to generate the executed code module; and

identifying at least a portion of the identified source code module as the source code segment.

3. The method of claim 1, where linking the identified source code segment to the test case that generated the test case error comprises storing an identifier of the test case error, a source code link to the linked source code segment, and a stack trace associated with the test case error as defect monitoring and tracking information.

4. The method of claim 1, where monitoring the linked source code segment for code changes comprises checking a code repository for at least one code change of the linked source code segment and further comprising:

identifying the at least one code change of the linked source code segment within the code repository as the detected code change.

5. The method of claim 4, where checking the code repository for the at least one code change of the linked source code segment comprises checking the code repository for the at least one code change in response to expiration of at least one of a configured plurality of time intervals.

6. The method of claim 1, where determining whether the test case re-execution criterion associated with the test case has been satisfied based upon the detected code change of the linked source code segment comprises determining whether a code change threshold has been exceeded, where the code change threshold is configured based upon one of a test case priority of the test case and a length of execution time of the test case.

7. The method of claim 1, where determining whether the test case re-execution criterion associated with the test case has been satisfied based upon the detected code change of the linked source code segment comprises at least one of:

comparing a stack trace associated with the test case error with a new version of the linked source code segment; and

one of;

determining whether the new version of the linked source code segment has diverged from the identified source code segment linked to the test case error and referenced by the stack trace; and

determining that a function named in the stack trace has been one of deleted, renamed, and moved to a different source code file.

8. The method of claim 1, further comprising:

re-executing the test case in response to the generation of the indication to re-execute the test case;

receiving a result output from the re-execution of the test case; and

appending the result output to the test case.