Lightweight software test library for vehicle compute hardware coverage testing
US-12124356-B2 · Oct 22, 2024 · US
US9477580B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9477580-B2 |
| Application number | US-201414223122-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 24, 2014 |
| Priority date | Dec 9, 2013 |
| Publication date | Oct 25, 2016 |
| Grant date | Oct 25, 2016 |
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 computer-implemented method, computer program product, and system is provided for determining test coverage. In an implementation, a method may include identifying at least one change in source code. The method may also include instrumenting object code of at least one class file associated with a source file of the source code associated with the identified at least one change. The method may further include testing the instrumented object code with at least one test case. The method may further include generating a coverage report associated with the instrumented object code, wherein the coverage report includes a proportion of the at least one change in the source code covered by the at least one test case.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: identifying, by a processor, at least one change in source code; identifying, by the processor, object code of at least one class file associated with a source file of the source code associated with the identified at least one change, wherein the object code of at least one class file is a compiled file of the source code; instrumenting, by the processor, the object code of the at least one class file associated with the source file of the source code associated with the identified at least one change; inserting a counter into the object code of the at least one class file associated with the source file of the source code associated with the identified at least one change, wherein the counter is increased each time a portion of an instruction associated with the object code is executed; testing, by the processor, the instrumented object code with at least one test case; and generating, by the processor, a coverage report associated with the instrumented object code, wherein the coverage report includes a proportion of the at least one change in the source code covered by the at least one test case. 2. The computer-implemented method of claim 1 , wherein identifying the at least one change in the source code includes identifying the at least one change in the source code based upon, at least in part, a source code history change-set. 3. The computer-implemented method of claim 1 , wherein the at least one change in the source code includes at least one of a new source file and at least one change in an existing source file. 4. The computer-implemented method of claim 3 , further including: identifying the at least one class file associated with the source file of the source code associated with the at least one change based upon, at least in part, a source code attribute of the at least one class file. 5. The computer-implemented method of claim 4 , wherein instrumenting the object code of the at least one class file associated with the source file of the source code associated with the identified at least one change further includes: instrumenting the object code associated with the at least one class file associated with the new source file. 6. The computer-implemented method of claim 4 , wherein instrumenting the object code of the at least one class file associated with the source file of the source code associated with the identified at least one change further includes: instrumenting the object code associated with the at least one class file associated with the at least one change in the existing source file.
Software maintenance or management · CPC title
for coverage analysis · CPC title
Image based installation; Cloning; Build to order · CPC title
Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title
Transformation of program code · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.