Identifying regression test failures

Patent metadata

Field	Value
Publication number	US-12189515-B2
Application number	US-202217577844-A
Country	US
Kind code	B2
Filing date	Jan 18, 2022
Priority date	Jan 18, 2022
Publication date	Jan 7, 2025
Grant date	Jan 7, 2025

Abstract

Examples described herein provide a computer-implemented method for identifying regression test failures that includes comparing a base code to a new code to locate an updated aspect of a program. The method further includes inserting debug code into corresponding source files for each of the base code and the new code for the updated aspect. The method further includes building a first image for the base code and a second image for the new code, the first and second images running in respective first and second containers. The method further includes comparing debugging outputs from a regression test of the respective first and second containers to identify a regression test failure. The method further includes implementing a corrective action to correct the regression test failure.

First claim

What is claimed is:

1. A computer-implemented method for identifying regression test failures, the method comprising:
comparing a base code to a new code to locate an updated aspect of a program to identify changes in the new code from the base code and a location of the changes;
generating a table that includes a unique identifier for each of the identified changes in the new code from the base code, a function associated with each of the identified changes, and a list of variables affected by each of the identified changes;
inserting, at the location of the changes, debug code into corresponding source files for each of the base code and the new code for the updated aspect, wherein the debug code includes a key tracing code for functions and variables affected by the updated aspect of the program and wherein the debug code is configured to output container-related information upon execution;
building a first image for the base code and a second image for the new code, the first and second images running in respective first and second containers;
comparing debugging outputs from a regression test of the respective first and second containers to identify a regression test failure, wherein identifying the regression test failure includes identifying that the regression test failed because a global variable was too large; and
implementing a corrective action to correct the regression test failure.

2. The computer-implemented method of claim 1 , wherein the updated aspect comprises at least one of an updated function, an updated variable, or updated runtime information.

3. The computer-implemented method of claim 1 , further comprising defining a configuration file to request a compiler to generate the debugging outputs.

4. The computer-implemented method of claim 1 , wherein comparing the base code to the new code to locate the updated aspect of the program comprises identifying one or both of affected local functions and affected local variables.

5. The computer-implemented method of claim 1 , further comprising, subsequent to building the first image and the second image, performing the regression test against the first image and the second image to generate the debugging outputs.

6. The computer-implemented method of claim 1 , wherein comparing the base code to the new code to locate the updated aspect of the program comprises identifying a change in a value assigned to a variable between the new code from the base code.

7. The computer-implemented method of claim 1 , wherein comparing the base code to the new code to locate the updated aspect of the program comprises identifying a difference between operations performed to a variable between the new code from the base code.

8. A system comprising:
a memory comprising computer readable instructions; and
a processing device for executing the computer readable instructions, the computer readable instructions controlling the processing device to perform operations comprising:
comparing a base code to a new code to locate an updated aspect of a program to identify changes in the new code from the base code and a location of the changes;
generating a table that includes a unique identifier for each of the identified changes in the new code from the base code, a function associated with each of the identified changes, and a list of variables affected by each of the identified changes;
inserting, at the location of the changes, debug code into corresponding source files for each of the base code and the new code for the updated aspect, wherein the debug code includes a key tracing code for functions and variables affected by the updated aspect of the program;
building a first image for the base code and a second image for the new code, the first and second images running in respective first and second containers;
comparing debugging outputs from a regression test of the respective first and second containers to identify a regression test failure, wherein identifying the regression test failure includes identifying that the regression test failed because a global variable was too large; and
implementing a corrective action to correct the regression test failure.

9. The system of claim 8 , wherein the updated aspect comprises at least one of an updated function, an updated variable, or updated runtime information.

10. The system of claim 8 , the operations further comprising defining a configuration file to request a compiler to generate the debugging outputs.

11. The system of claim 8 , wherein comparing the base code to the new code to locate the updated aspect of the program comprises identifying one or both of affected local functions and affected local variables.

12. The system of claim 8 , further comprising, subsequent to building the first image and the second image, performing the regression test against the first image and the second image to generate the debugging outputs.

13. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform operations comprising:
comparing a base code to a new code to locate an updated aspect of a program to identify changes in the new code from the base code and a location of the changes;
generating a table that includes a unique identifier for each of the identified changes in the new code from the base code, a function associated with each of the identified changes, and a list of variables affected by each of the identified changes;
inserting, at the location of the changes, debug code into corresponding source files for each of the base code and the new code for the updated aspect, wherein the debug code includes a key tracing code for functions and variables affected by the updated aspect of the program;
building a first image for the base code and a second image for the new code, the first and second images running in respective first and second containers;
comparing debugging outputs from a regression test of the respective first and second containers to identify a regression test failure, wherein identifying the regression test failure includes identifying that the regression test failed because a global variable was too large; and
implementing a corrective action to correct the regression test failure.

14. The computer program product of claim 13 , wherein the updated aspect comprises at least one of an updated function, an updated variable, or updated runtime information.

15. The computer program product of claim 13 , the operations further comprising defining a configuration file to request a compiler to generate the debugging outputs.

16. The computer program product of claim 13 , wherein comparing the base code to the new code to locate the updated aspect of the program comprises identifying one or both of affected local functions and affected local variables.

Assignees

• IBM

Inventors

• Li Xiao-Yu
• Fan hua wei
• Deng Jiangang
• Sun Hong Wei
• Chen xiao ling
• Huang wen ji

Classifications

• G06F11/3698

  Environments for analysis, debugging or testing of software · CPC title

• G06F11/3692 Primary

  for test results analysis · CPC title

• G06F11/3624 Primary

  by performing operations on the source code, e.g. via a compiler · CPC title

• G06F11/368

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

• G06F11/3688

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