GUARDING CODE CHECK-IN WITH TEST CASE EXECUTION RESULTS

• US 20100058294A1
• Filed: 08/27/2008
• Published: 03/04/2010
• Est. Priority Date: 08/27/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Best, Debora O'Berry, Girouard, Janice Marie, Best, Steven Francis, Eggers, Robert James JR.
• Granted Patent: US 8,312,430 B2
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A mechanism for providing a source code control system that employs test case execution results to mandate that software code have a specific level of quality for check-in to a central repository. A request to check-in a modified copy of a source code file to a repository is received, wherein the modified copy comprises changes to the source code file located in the repository. The modified copy of the source code file is placed in a quality check pending state in the repository. Responsive to an occurrence of a specific event or expiration of a set time period, applicable regression test cases are executed against the changes in the modified copy. A determination is made as to whether the regression test cases are successful. If the regression test cases are successful, the changes in the modified copy are committed to the source code file located in the repository.

Claims

1. A computer implemented method for automating software code check-in in a code management system, the computer implemented method comprising:

receiving a request to check-in a modified copy of a source code file to a repository, wherein the modified copy comprises changes to the source code file located in the repository;

placing the modified copy of the source code file in a quality check pending state in the repository;

responsive to an occurrence of a specific event or expiration of a set time period, executing regression test cases against the changes in the modified copy;

determining if the regression test cases are successful; and

responsive to a determination that the regression test cases are successful, committing the changes in the modified copy to the source code file located in the repository.

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

responsive to a determination that the regression test cases are not successful, preventing the modified copy from being committed to the repository.

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

responsive to a determination that the regression test cases are not successful, backing out the modified copy from the quality check pending state.

4. The computer implemented method of claim 3, further comprising:

providing notification that the regression test cases were unsuccessful.

5. The computer implemented method of claim 1, wherein the regression test cases automatically test the modified copy of the source code file to verify the modified copy meets a minimum level of acceptable code quality before being committed to the repository.

6. The computer implemented method of claim 1, wherein placing the modified copy of the source code file in a quality check pending state in the repository further comprises:

pulling the modified code into a software delivery environment; and

performing a build process on the modified code in the software delivery environment, wherein appropriate regression test buckets are automatically triggered in the build process to test a quality of the modified code.

7. The computer implemented method of claim 1, wherein committing the changes in the modified copy to the source code file located in the repository further comprises:

moving the modified copy from the quality check pending state to a permanent state in the repository.

8. The computer implemented method of claim 1, further comprising:

responsive to a determination that the regression test cases are not successful, separating the changes in the modified copy into change sub groups;

re-executing the regression test cases on each separate change sub group; and

responsive to a determination that the re-executed regression test cases are unsuccessful against a change sub group, iteratively performing the separating and re-executing steps on the change sub group to locate a change in the modified copy that caused the regression test cases to fail.

9. A computer program product for automating software code check-in in a code management system, the computer program product comprising:

a computer usable medium having computer usable program code tangibly embodied thereon, the computer usable program code comprising;

computer usable program code for receiving a request to check-in a modified copy of a source code file to a repository, wherein the modified copy comprises changes to the source code file located in the repository;

computer usable program code for placing the modified copy of the source code file in a quality check pending state in the repository;

computer usable program code for executing regression test cases against the changes in the modified copy in response to an occurrence of a specific event or expiration of a set time period;

computer usable program code for determining if the regression test cases are successful; and

computer usable program code for committing the changes in the modified copy to the source code file located in the repository in response to a determination that the regression test cases are successful.

10. The computer program product of claim 9, further comprising:

computer usable program code for preventing the modified copy from being committed to the repository in response to a determination that the regression test cases are not successful.

11. The computer program product of claim 9, further comprising:

computer usable program code for backing out the modified copy from the quality check pending state in response to a determination that the regression test cases are not successful.

12. The computer program product of claim 11, further comprising:

computer usable program code for providing notification that the regression test cases were unsuccessful.

13. The computer program product of claim 9, wherein the regression test cases automatically test the modified copy of the source code file to verify the modified copy meets a minimum level of acceptable code quality before being committed to the repository.

14. The computer program product of claim 9, wherein the computer usable program code for placing the modified copy of the source code file in a quality check pending state in the repository further comprises:

computer usable program code for pulling the modified code into a software delivery environment; and

computer usable program code for performing a build process on the modified code in the software delivery environment, wherein appropriate regression test buckets are automatically triggered in the build process to test a quality of the modified code.

15. The computer program product of claim 9, wherein the computer usable program code for committing the changes in the modified copy to the source code file located in the repository further comprises:

computer usable program code for moving the modified copy from the quality check pending state to a permanent state in the repository.

16. The computer program product of claim 9, further comprising:

computer usable program code for separating the changes in the modified copy into change sub groups in response to a determination that the regression test cases are not successful;

computer usable program code for re-executing the regression test cases on each separate change sub group; and

computer usable program code for iteratively performing, in response to a determination that the re-executed regression test cases are unsuccessful against a change sub group, the separating and re-executing steps on the change sub group to locate a change in the modified copy that caused the regression test cases to fail.

17. A data processing system for automating software code check-in in a code management system, the data processing system comprising:

a bus;

a storage device connected to the bus, wherein the storage device contains computer usable code;

at least one managed device connected to the bus;

a communications unit connected to the bus; and

a processing unit connected to the bus, wherein the processing unit executes the computer usable code to receive a request to check-in a modified copy of a source code file to a repository, wherein the modified copy comprises changes to the source code file located in the repository;

place the modified copy of the source code file in a quality check pending state in the repository;

execute regression test cases against the changes in the modified copy in response to an occurrence of a specific event or expiration of a set time period;

determine if the regression test cases are successful; and

commit the changes in the modified copy to the source code file located in the repository in response to a determination that the regression test cases are successful.

18. The data processing system of claim 17, wherein the processing unit further executes the computer usable code to back out the modified copy from the quality check pending state in response to a determination that the regression test cases are not successful.

19. The data processing system of claim 18, wherein the processing unit further executes the computer usable code to provide notification that the regression test cases were unsuccessful.

20. The data processing system of claim 17, wherein the regression test cases automatically test the modified copy of the source code file to verify the modified copy meets a minimum level of acceptable code quality before being committed to the repository.