# US 2020/0394127 A1 · Fault detection using breakpoint value-based fingerprints of failing regression test cases

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0394127 A1
- Document ID: US20200394127A1
- Status: Published application
- Kind: A1
- Application number: 16/440,810
- Filed: 2019-06-13
- Published: 2020-12-17
- Earliest claimed: 2019-06-13
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: ANDREW HICKS; DALE E. BLUE; RYAN THOMAS RAWLINS; STEVEN M. PARTLOW
- Web page: https://patentgrep.com/patent/US20200394127A1

## CPC

- G06F 11/3684: {for test design, e.g. generating new test cases}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 11/3692: {for test results analysis}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods, and computer-readable media are described for utilizing breakpoint value-based fingerprints of failing regression test cases to determine specific components of a System Under Test (SUT) that are causing a fault such as specific lines of source code. A failing test case from a regression run is selected and fault localization and inverse combinatorics techniques are employed to generate a set of failing test cases around the selected failing test case. A set of test fingerprints corresponding to the set of failing test cases is compared to a set of test fingerprints corresponding to a set of passing test cases to determine breakpoints that are indicated as being encountered during execution of at least one failing test case and that are not encountered during execution of any of the passing test cases. Specific lines of source code that correspond to these breakpoints are then identified as causing the fault.

## Claims

### Claim 1

A computer-implemented method for performing fault detection, the method comprising:
executing a set of test cases on source code;
determining that one or more test cases in the set of test cases fail to successfully execute;
selecting a particular failing test case from the one or more test cases that fail to successfully execute;
generating a set of failing test cases based on the particular failing test case;
determining a first set of fingerprints respectively corresponding to the set of failing test cases;
determining a second set of fingerprints respectively corresponding to a set of passing test cases that successfully execute on the source code; and
determining, based at least in part on a comparison of the first set of fingerprints to the second set of fingerprints, one or more lines of the source code that are contributing to a fault.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising presenting, via a user interface, an indication of the one or more lines of the source code.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein determining the one or more lines of the source code that are contributing to the fault comprises:
determining a set of breakpoint encounters that are present in the first set of fingerprints and absent from the second set of fingerprints; and
determining the one or more lines of the source code based at least in part on a correspondence between the one or more lines of the source code and the set of breakpoint encounters.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein determining the set of breakpoint encounters comprises:
determining a value contained in a particular fingerprint in the first set of fingerprints, wherein the value is stored at an index in the particular fingerprint that corresponds to a particular breakpoint in the source code;
determining that the value indicates that the particular breakpoint is encountered at least once during execution of a particular failing test case that corresponds to the particular fingerprint; and
determining that no fingerprint in the second set of fingerprints includes any value that indicates that the particular breakpoint is encountered during execution of any passing test case.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein determining the one or more lines of the source code based at least in part on the correspondence between the one or more lines of the source code and the set of breakpoint encounters comprises determining a particular line of the source code that corresponds to the particular breakpoint.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, further comprising:
executing the set of failing test cases on the source code;
determining a respective code path traversed by each test case of the set of failing test cases; and
determining, based at least in part on each respective code path, a respective fingerprint in the first set of fingerprints.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein generating the set of failing test cases from the particular failing test case comprises:
determining a particular combination of attribute values causing the particular failing test case to fail to successfully execute;
determining a set of test vectors, wherein each test vector includes the particular combination of attribute values and a respective one or more additional attribute values; and
generating the set of failing test cases from the set of test vectors.

### Claim 8

A system for performing fault detection, the system comprising:
at least one processor; and
at least one memory storing computer-executable instructions, wherein the at least one processor is configured to access the at least one memory and execute the computer-executable instructions to:
execute a set of test cases on source code;
determine that one or more test cases in the set of test cases fail to successfully execute;
select a particular failing test case from the one or more test cases that fail to successfully execute;
generate a set of failing cases based on the particular failing test case;
determine a first set of fingerprints respectively corresponding to the set of failing test cases;
determine a second set of fingerprints respectively corresponding to a set of passing test cases that successfully execute on the source code; and
determine, based at least in part on a comparison of the first set of fingerprints to the second set of fingerprints, one or more lines of the source code that are contributing to a fault.

### Claim 9 (depends on 8)

The system of claim 8, wherein the at least one processor is further configured to execute the computer-executable instructions to present, via a user interface, an indication of the one or more lines of the source code.

### Claim 10 (depends on 8)

The system of claim 8, wherein the at least one processor is configured to determine the one or more lines of the source code that are contributing to the fault by executing the computer-executable instructions to:
determine a set of breakpoint encounters that are present in the first set of fingerprints and absent from the second set of fingerprints; and
determine the one or more lines of the source code based at least in part on a correspondence between the one or more lines of the source code and the set of breakpoint encounters.

### Claim 11 (depends on 10)

The system of claim 10, wherein the at least one processor is configured to determine the set of breakpoint encounters by executing the computer-executable instructions to:
determine a value contained in a particular fingerprint in the first set of fingerprints, wherein the value is stored at an index in the particular fingerprint that corresponds to a particular breakpoint in the source code;
determine that the value indicates that the particular breakpoint is encountered at least once during execution of a particular failing test case that corresponds to the particular fingerprint; and
determine that no fingerprint in the second set of fingerprints includes any value that indicates that the particular breakpoint is encountered during execution of any passing test case.

### Claim 12 (depends on 11)

The system of claim 11, wherein the at least one processor is configured to determine the one or more lines of the source code based at least in part on the correspondence between the one or more lines of the source code and the set of breakpoint encounters by executing the computer-executable instructions to determine a particular line of the source code that corresponds to the particular breakpoint.

### Claim 13 (depends on 8)

The system of claim 8, wherein the at least one processor is further configured to execute the computer-executable instructions to:
execute the set of failing test cases on the source code;
determine a respective code path traversed by each test case of the set of failing test cases; and
determine, based at least in part on each respective code path, a respective fingerprint in the first set of fingerprints.

### Claim 14 (depends on 8)

The system of claim 8, wherein the at least one processor is configured to generate the set of failing test cases from the particular failing test case by executing the computer-executable instructions to:
determine a particular combination of attribute values causing the particular failing test case to fail to successfully execute;
determine a set of test vectors, wherein each test vector includes the particular combination of attribute values and a respective one or more additional attribute values; and
generate the set of failing test cases from the set of test vectors.

### Claim 15

A computer program product for performing fault detection, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions readable by a processing circuit to cause the processing circuit to perform a method comprising:
executing a set of test cases on source code;
determining that one or more test cases in the set of test cases fail to successfully execute;
selecting a particular failing test case from the one or more test cases that fail to successfully execute;
generating a set of failing test cases based on the particular failing test case;
determining a first set of fingerprints respectively corresponding to the set of failing test cases;
determining a second set of fingerprints respectively corresponding to a set of passing test cases that successfully execute on the source code; and
determining, based at least in part on a comparison of the first set of fingerprints to the second set of fingerprints, one or more lines of the source code that are contributing to a fault.

### Claim 16 (depends on 15)

The computer program product of claim 15, the method further comprising presenting, via a user interface, an indication of the one or more lines of the source code.

### Claim 17 (depends on 15)

The computer program product of claim 15, wherein determining the one or more lines of the source code that are contributing to the fault comprises:
determining a set of breakpoint encounters that are present in the first set of fingerprints and absent from the second set of fingerprints; and
determining the one or more lines of the source code based at least in part on a correspondence between the one or more lines of the source code and the set of breakpoint encounters.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein determining the set of breakpoint encounters comprises:
determining a value contained in a particular fingerprint in the first set of fingerprints, wherein the value is stored at an index in the particular fingerprint that corresponds to a particular breakpoint in the source code;
determining that the value indicates that the particular breakpoint is encountered at least once during execution of a particular failing test case that corresponds to the particular fingerprint; and
determining that no fingerprint in the second set of fingerprints includes any value that indicates that the particular breakpoint is encountered during execution of any passing test case.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein determining the one or more lines of the source code based at least in part on the correspondence between the one or more lines of the source code and the set of breakpoint encounters comprises determining a particular line of the source code that corresponds to the particular breakpoint.

### Claim 20 (depends on 15)

The computer program product of claim 15, the method further comprising:
executing the set of failing test cases on the source code;
determining a respective code path traversed by each test case of the set of failing test cases; and
determining, based at least in part on each respective code path, a respective fingerprint in the first set of fingerprints.
