Probationary software tests

• US 10,229,034 B2
• Filed: 11/29/2016
• Issued: 03/12/2019
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chan, Philip S. P., Hey, Laurence A., Izard, William J., Ponsford, Matthew
• Primary Examiner(s): Dao, Thuy
• Application Number:
  US15/363,469
• Publication Number:
  US 20170075796A1
• Time in Patent Office: 833 Days
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3676 for coverage analysis
• CPC Class Codes: G06F 11/3692 for test results analysis

Abstract

A method, computer program product, and system is described. A continuous integration environment is identified. A first software test associated with the continuous integration environment is identified. A probationary status for the first software test is determined, the probationary status indicating, at least in part, a potential lack of reliability for the first software test.

Claims

1. A computer-implemented method comprising:

identifying, by one or more computing devices, a continuous integration environment;

identifying, by the one or more computing devices, a first software test associated with the continuous integration environment;

identifying, by the one or more computing device, a second software test associated with the continuous integration environment, the second software test having a promoted status;

determining, by the one or more computing devices, a probationary status for the first software test based upon, at least in part, a recency with which the first software test was associated with the continuous integration environment relative to a recency with which another software test was associated with the continuous integration environment with respect to the date the other software test was introduced to the continuous integration environment or the last time the other software test was edited in the continuous integration environment, the probationary status indicating, at least in part, a potential lack of reliability for the first software test;

determining intermittent reliability of the first software test having a promoted status based upon, at least in part, an intermittent pattern of pass/fail results with respect to a particular codebase;

providing an alert based upon, at least in part, the determined intermittent reliability of the first software test; and

presenting, by the one or more computing devices, in a first format, first test result information associated with running the first software test and presenting, in a second format, second test result information associated with the second software test, wherein the first format is distinct from the second format based upon, at least in part, the probationary status of the first software test and the promoted status of the second software test, and wherein one or more of the first test result information and the second test result information include an aggregate pass/fail rate.

2. The computer-implemented method of claim 1 further comprising:

determining a promoted status for the first software test based upon, at least in part, identifying a sequence of successful runs for the first software test.

3. The computer-implemented method of claim 1 further comprising:

determining a promoted status for the first software test based upon, at least in part, identifying a code consistency over a sequence of runs for the first software test.

4. The computer-implemented method of claim 1 wherein identifying the probationary status is based upon, at least in part:

storing, in a test result database, first test result information associated with running the first software test; and

comparing the first test result information with other test result information in the test result database in order to, at least in part, identify an indicator of the potential lack of reliability for the first software test.

5. The computer-implemented method of claim 1 wherein identifying the probationary status is based upon, at least in part:

identifying the first software test as a previously-promoted software test; and

determining an intermittent reliability of the first software test.

6. A computer program product residing on a non-transitory computer-readable storage medium having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform operations comprising:

identifying a continuous integration environment;

identifying a first software test associated with the continuous integration environment;

identifying a second software test associated with the continuous integration environment, the second software test having a promoted status;

determining a probationary status for the first software test based upon, at least in part, a recency with which the first software test was associated with the continuous integration environment relative to a recency with which another software test was associated with the continuous integration environment with respect to the date the other software test was introduced to the continuous integration environment or the last time the other software test was edited in the continuous integration environment, the probationary status indicating, at least in part, a potential lack of reliability for the first software test;

determining intermittent reliability of the first software test having a promoted status based upon, at least in part, an intermittent pattern of pass/fail results with respect to a particular codebase;

providing an alert based upon, at least in part, the determined intermittent reliability of the first software test; and

presenting, in a first format, first test result information associated with running the first software test and presenting, in a second format, second test result information associated with the second software test, wherein the first format is distinct from the second format based upon, at least in part, the probationary status of the first software test and the promoted status of the second software test, and wherein one or more of the first test result information and the second test result information include an aggregate pass/fail rate.

7. The computer program product of claim 6 wherein the operations further comprise:

determining a promoted status for the first software test based upon, at least in part, identifying a sequence of successful runs for the first software test.

8. The computer program product of claim 6 wherein the operations further comprise:

determining a promoted status for the first software test based upon, at least in part, identifying a code consistency over a sequence of runs for the first software test.

9. The computer program product of claim 6 wherein identifying the probationary status is based upon, at least in part:

storing, in a test result database, first test result information associated with running the first software test; and

comparing the test result information with other test result information in the test result database in order to, at least in part, identify an indicator of the potential lack of reliability for the first software test.

10. The computer program product of claim 6 wherein identifying the probationary status is based upon, at least in part:

identifying the first software test as a previously-promoted software test; and

determining an intermittent reliability of the first software test.

11. A computer system comprising:

one or more processor devices; and

one or more memory architectures coupled with the one or more processor devices;

wherein the one or more processor devices are configured to;

identify a continuous integration environment;

identify a first software test associated with the continuous integration environment;

identify a second software test associated with the continuous integration environment, the second software test having a promoted status;

determine a probationary status for the first software test based upon, at least in part, a recency with which the first software test was associated with the continuous integration environment relative to a recency with which another software test was associated with the continuous integration environment with respect to the date the other software test was introduced to the continuous integration environment or the last time the other software test was edited in the continuous integration environment, the probationary status indicating, at least in part, a potential lack of reliability for the first software test;

determining intermittent reliability of the first software test having a promoted status based upon, at least in part, an intermittent pattern of pass/fail results with respect to a particular codebase;

providing an alert based upon, at least in part, the determined intermittent reliability of the first software test; and

present, in a first format, first test result information associated with running the first software test and presenting, in a second format, second test result information associated with the second software test, wherein the first format is distinct from the second format based upon, at least in part, the probationary status of the first software test and the promoted status of the second software test, and wherein one or more of the first test result information and the second test result information include an aggregate pass/fail rate.

12. The computer system of claim 11 wherein the one or more processor devices are further configured to:

determine a promoted status for the first software test based upon, at least in part, one or more of;

identifying a sequence of successful runs for the first software test; and

identifying a code consistency over a sequence of runs for the first software test.

13. The computer system of claim 11 wherein identifying the probationary status is based upon, at least in part:

storing, in a test result database, test result information associated with running the first software test; and

comparing the test result information with other test result information in the test result database in order to, at least in part, identify an indicator of the potential lack of reliability for the first software test.

14. The computer system of claim 11 wherein identifying the probationary status is based upon, at least in part:

identifying the first software test as a previously-promoted software test; and

determining an intermittent reliability of the first software test.