TREND BASED TEST FAILURE PRIORITIZATION

• US 20090292956A1
• Filed: 05/23/2008
• Published: 11/26/2009
• Est. Priority Date: 05/23/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hardy, D. Gordon, Niemeyer, Patrick, Rivera, Carlo
• Application Number:
  US12/125,927
• Publication Number:
  US 20090292956A1
• Time in Patent Office: Days
• US Class Current: 714/48
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

Various technologies and techniques are disclosed for using historical trends from prior tests to prioritize how failures are reported in later tests. After a user changes a software development project, one or more tests are run to detect failures during execution of the tests. Any detected failures are analyzed in comparison with historical failures for the software development project across tests run for multiple users. Any detected failures are categorized as new or old. New failures are reported with a different emphasis than old failures, such as with new failures being reported as a higher priority than old failures.

Claims

1. A method for utilizing historical software execution failures from prior tests to prioritize how failures are reported in later tests comprising the steps of:

after a user changes a software development project, running one or more tests to detect failures during execution of the tests;

analyzing any detected failures in comparison with historical failures for the software development project across tests run for multiple users;

categorizing any detected failures as new or old; and

reporting new failures with a different emphasis than old failures.

2. The method of claim 1, wherein the historical failures are stored in a central data store accessible to the multiple users.

3. The method of claim 1, wherein new failures are reported in a list of failures with a higher priority than old failures.

4. The method of claim 1, wherein old failures introduced by the user are reported in a list of failures with a higher priority than old failures of other users.

5. The method of claim 1, wherein new failures are displayed with a visual indicator.

6. The method of claim 1, wherein the reporting step is performed by emailing a test failure report.

7. The method of claim 1, wherein the reporting step is performed by displaying a test failure report in an interactive test tool.

8. The method of claim 1, wherein the one or more tests are performed before the user checks in source code for the software development project to a central source code repository.

9. The method of claim 1, wherein the one or more tests are executed by an automated testing tool.

10. The method of claim 9, wherein the automated testing tool is responsible for performing the reporting step.

11. A method for prioritizing test failures based on analysis of historical failures across multiple users comprising the steps of:

gathering current failure information from one or more tests of a software development application for a current user;

gathering historical failure information from failures occurring in past test runs;

comparing current failure information to historical failure information to determine if any failures have occurred in past test runs; and

reporting any failures that have not occurred in past test runs as higher priority than any failures that have occurred in past test runs.

12. The method of claim 11, wherein historical failure information is gathered by accessing a data store of historical failures.

13. The method of claim 11, further comprising the steps of:

reporting any failures that have occurred in past test runs for the current user as higher priority than any failures that have occurred in past test runs for other users.

14. The method of claim 11, wherein the reporting step is performed by emailing a test failure report to one or more users.

15. The method of claim 11, wherein the reporting step is performed by displaying a test failure report in an interactive test tool.

16. The method of claim 11, wherein new failures are displayed with a visual indicator.

17. The method of claim 11, wherein the one or more tests are executed by an automated testing tool.

18. The method of claim 17, wherein the automated testing tool is responsible for performing the reporting step.

19. A computer-readable medium having computer-executable instructions for causing a computer to perform steps comprising:

gathering current failure information from one or more automated tests of a software development application for a current user;

gathering historical failure information from failures occurring in past automated test runs of the software development application for all users;

comparing current failure information to historical failure information to determine if any failures have occurred in past test runs;

reporting any failures that have not occurred in past automated test runs in a first priority grouping of failures;

reporting any failures that have occurred in past automated test runs for the current user in a second priority grouping of failures; and

reporting any failures that have occurred in past automated test runs for other users in a third priority grouping of failures.

20. The computer-readable medium of claim 19, wherein the historical failure information is stored in a central data store.