Proactive and selective regression testing based on historic test results

Patent metadata

Field	Value
Publication number	US-2017139815-A1
Application number	US-201615052931-A
Country	US
Kind code	A1
Filing date	Feb 25, 2016
Priority date	Nov 18, 2015
Publication date	May 18, 2017
Grant date	—

Abstract

In an approach to reducing regression test duration, one or more computer processors receive a first code change. The one or more computer processors retrieve one or more historic code changes relevant to the first code change. The one or more computer processors determine whether one or more failed test cases are relevant to the one or more historic code changes, where the one or more relevant failed test cases and the one or more historic code changes are stored in a table of test history. In response to determining the one or more historic code changes are relevant to one or more failed test cases, the one or more computer processors retrieve the one or more relevant failed test cases from the table of test history.

First claim

What is claimed is:

1 . A method for reducing regression test duration, the method comprising:
receiving, by one or more computer processors, a first code change; retrieving, by the one or more computer processors, one or more historic code changes relevant to the first code change, wherein retrieving one or more historic code changes relevant to the first code change comprises determining, by the one or more computer processors, a positional overlap of the first code change to the one or more historic code changes, wherein relevance is based on the determined positional overlap at a line level; determining, by the one or more computer processors, whether one or more failed test cases are relevant to the one or more historic code changes, wherein the one or more relevant failed test cases and the one or more historic code changes are stored in a table of test history; and responsive to determining the one or more historic code changes are relevant to one or more failed test cases, retrieving, by the one or more computer processors, the one or more relevant failed test cases from the table of test history.

2 . The method of claim 1 , wherein the table of test history links one or more failed test cases to one or more historic code changes.

3 . The method of claim 2 , wherein the table of test history links corresponding metadata to the one or more failed test cases and the one or more historic code changes, wherein the corresponding metadata includes at least one of: a date of occurrence, an associated defect, a severity of a failure, an identification of a coder that made a change, an age of an entry, a number of failing test cases attributed to a code change, a size of a code change, a scope of a code change, a level of experience of a submitting coder, and a time of day a change was submitted.

4 . The method of claim 1 , wherein the determined positional overlap is at one of a file level, an object level, or a component level.

5 . The method of claim 1 , further comprising, responsive to retrieving the one or more relevant test cases in the table of test history, notifying, by the one or more computer processors, a user.

6 . The method of claim 1 , further comprising:
receiving, by the one or more computer processors, regression test results, wherein the regression test results include at least one failing test case; querying, by the one or more computer processors, the table of test history for the at least one failing test case; and determining, by the one or more computer processors, whether at least one historic code change corresponding to the at least one failing test case is relevant to at least one current code change.

7 . The method of claim 6 , further comprising, responsive to determining at least one historic code change corresponding to the at least one failing test case is relevant to at least one current code change, notifying, by the one or more computer processors, a user.

8 . The method of claim 6 , wherein determining at least one historic code change corresponding to the at least one failing test case is relevant to at least one current code change further comprises determining, by the one or more computer processors, positional overlap of the at least one current code change to the at least one historic code change, wherein relevance is based on the determined positional overlap and is at one of a file level, a line level, an object level, or a component level.

Assignees

• IBM

Inventors

• D'Andrea Adam K
• Elliott Jenna R
• Khan Fahad A
• Kwong Raymond C
• Mcintyre Chad J
• Sadeghian Sadeghabad Sina

Classifications

• G06F11/3672 Primary

  Test management · CPC title

• G06F11/3688 Primary

  for test execution, e.g. scheduling of test suites · CPC title

• G06F11/368

  for test version control, e.g. updating test cases to a new software version · CPC title

• G06F11/3692

  for test results analysis · CPC title