Incremental code coverage analysis using automatic breakpoints
US-2017132121-A1 · May 11, 2017 · US
US10949172B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-10949172-B1 |
| Application number | US-201816163458-A |
| Country | US |
| Kind code | B1 |
| Filing date | Oct 17, 2018 |
| Priority date | Nov 14, 2017 |
| Publication date | Mar 16, 2021 |
| Grant date | Mar 16, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system, method, and computer program product are provided for determining incremental code coverage of a software project. In operation, a system provides computation of project specific incremental (delta) code coverage in parallel in scenarios of multiple project teams working on different projects on a same module (or in the same repository). Further, an incremental code/mutation coverage analyzer engine associated with the system may be integrated with a project management tool and a version control software to obtain the changed code lines with respect to each project, using what it calculates as the incremental code and/or the mutation coverage.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: retrieving, by a system, a plurality of changelists associated with a plurality of software projects operating on a same source code of a program, wherein each changelist of the plurality of changelists indicates portions of the source code of the program that are changed by a corresponding software project of the plurality of software projects; identifying, by the system, one or more changed lines with respect to changed code within the program, utilizing the plurality of changelists, including for each changelist of each corresponding software project: determining, from the changelist, one or more files associated with the program that are changed by the software project, and comparing each file of the one or more files to an immediate previous version of the file to identify lines of code within the one or more files that are changed by the software project; obtaining, by the system, overall test coverage for the entire program in association with all of the plurality of software projects, by determining for each line of each file of each software project which instructions at the line are covered by unit tests for the software project; assessing, by the system, test coverage for the one or more changed lines in each software project of the plurality of software projects, from the overall test coverage obtained for the entire program; calculating, by the system independently for each software project of the plurality of software projects, incremental test coverage for the lines of code changed by the software project by: collating the overall test coverage obtained for the entire program by software project to compute a percentage of test coverage for each software project of the plurality of software projects; and reporting, by the system, the incremental test coverage calculated for each software project of the plurality of software projects. 2. The method of claim 1 , wherein the plurality of software projects are associated with a same module of the program but different software teams. 3. The method of claim 2 , wherein the incremental code coverage is calculated for each of the plurality of software projects such that the incremental code coverage is separately provided for each of the different software teams. 4. A non-transitory computer readable medium storing computer code executable by a processor to perform a method comprising: retrieving, by a system, a plurality of changelists associated with a plurality of software projects operating on a same source code of a program, wherein each changelist of the plurality of changelists indicates portions of the source code of the program that are changed by a corresponding software project of the plurality of software projects; identifying, by the system, one or more changed lines with respect to changed code within the program, utilizing the plurality of changelists, including for each changelist of each corresponding software project: determining, from the changelist, one or more files associated with the program that are changed by the software project, and comparing each file of the one or more files to an immediate previous version of the file to identify lines of code within the one or more files that are changed by the software project; obtaining, by the system, overall test coverage for the entire program in association with all of the plurality of software projects, by determining for each line of each file of each software project which instructions at the line are covered by unit tests for the software project; assessing, by the system, test coverage for the one or more changed lines in each software project of the plurality of software projects, from the overall test coverage obtained for the entire program; calculating, by the system independently for each software project of the plurality of software projects, incremental test coverage for the lines of code changed by the software project by: collating the overall test coverage obtained for the entire program by software project to compute a percentage of test coverage for each software project of the plurality of software projects; and reporting, by the system, the incremental test coverage calculated for each software project of the plurality of software projects. 5. The non-transitory computer readable medium of claim 4 , wherein the plurality of software projects are associated with a same module of the program but different software teams. 6. The non-transitory computer readable medium of claim 5 , wherein the incremental code coverage is calculated for each of the plurality of software projects such that the incremental code coverage is separately provided for each of the different software teams. 7. A system, comprising: a non-transitory memory storing instructions; and one or more processors in communication with the non-transitory memory that execute the instructions to perform a method comprising: retrieving a plurality of changelists associated with a plurality of software projects operating on a same source code of a program, wherein each changelist of the plurality of changelists indicates portions of the source code of the program that are changed by a corresponding software project of the plurality of software projects; identifying one or more changed lines with respect to changed code within the program, utilizing the plurality of changelists, including for each changelist of each corresponding software project: determining, from the changelist, one or more files associated with the program that are changed by the software project, and comparing each file of the one or more files to an immediate previous version of the file to identify lines of code within the one or more files that are changed by the software project; obtaining overall test coverage for the entire program in association with all of the plurality of software projects, by determining for each line of each file of each software project which instructions at the line are covered by unit tests for the software project; assessing test coverage for the one or more changed lines in each software project of the plurality of software projects, from the overall test coverage obtained for the entire program; calculating, independently for each software project of the plurality of software projects, incremental test coverage for the lines of code changed by the software project by: collating the overall test coverage obtained for the entire program by software project to compute a percentage of test coverage for each software project of the plurality of software projects; and reporting, by the system, the incremental test coverage calculated for each software project of the plurality of software projects.
Related publications grouped by family.
Answers are generated from the same data shown on this page.