Lightweight software test library for vehicle compute hardware coverage testing
US-12124356-B2 · Oct 22, 2024 · US
US2017075794A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017075794-A1 |
| Application number | US-201615140771-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 28, 2016 |
| Priority date | Sep 14, 2015 |
| Publication date | Mar 16, 2017 |
| Grant date | — |
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.
Computer implemented methods and systems are provided for computing code coverage in a system that includes a user system and a cloud-based computing platform. The user system includes a processing system, memory and an input system that receives input parameters specified by a user of the user system. The memory can store a source class filter module executable by the processing system. Upon being executed by the processing system, the source class filter module can, based on one or more of the input parameters, group and filter source class identifiers to generate a unique source class identifier array of filtered source class identifiers that correspond to a particular subset of source classes that targeted code coverage metrics are to be computed for during code coverage computations when testing an application. A code coverage computation unit can then compute the targeted code coverage metrics for the particular subset of source classes corresponding to the filtered source class identifiers of the unique source class identifier array.
Opening claim text (preview).
What is claimed: 1 . A system, comprising: a user system, comprising: an input system configured to receive input parameters specified by a user of the user system; a processing system; and memory configured to store: a source class filter module executable by the processing system, wherein the source class filter module, upon being executed by the processing system, is configured to: group and filter source class identifiers, based on one or more of the input parameters, to generate a unique source class identifier array of filtered source class identifiers that correspond to a particular subset of source classes that targeted code coverage metrics are to be computed during code coverage computations when testing an application; and a cloud-based computing platform, communicatively coupled to the user system, and comprising: a code coverage computation unit that is configured to compute the targeted code coverage metrics for the particular subset of source classes corresponding to the filtered source class identifiers of the unique source class identifier array. 2 . The system according to claim 1 , wherein the user system further comprises: a validation module configured to: evaluate each of the input parameters to determine whether each input parameter is valid, generate an error message when the validation module determines that any of the input parameters are not valid, and communicate the error message to a user interface of the user system. 3 . The system according to claim 1 , wherein the cloud-based computing platform further comprises: an interface that interfaces with the source class filter module, wherein the input parameters comprise: a manifest file specified by the user of the user system, and wherein the source class filter module comprises: a first source class fetcher comprising: a manifest file processor configured to: retrieve the manifest file, wherein the manifest file comprises a plurality of source class names that can be used to fetch a particular group of source class identifiers from a data store of the cloud-based computing platform; and a manifest file reader and query builder configured to: read the source class names from the manifest file, send the source class names from the manifest file to the interface, receive the source class identifiers corresponding to each of the source class names from the manifest file from the interface, and group the source class identifiers into a first source class identifier array. 4 . The system according to claim 3 , wherein the manifest file has a name, and wherein the plurality of source class names in the manifest file comprises: a statically defined set of source class names, where each of the source class names is associated with a source class and has a corresponding source class identifier that identifies that source class 5 . The system according to claim 4 wherein the application is a multi-tenant application, wherein the user selects the manifest file to specify the statically defined set of source class names that are of interest to a sub-tenant of the multi-tenant application during code coverage computations, and wherein the source classes associated with the statically defined set of source class names collectively correspond to particular source code of the multi-tenant application that is of interest to the sub-tenant of multi-tenant application. 6 . The system according to claim 3 , wherein the input parameters comprise: one or more regular expressions specified by the user of the user system, wherein each regular expression is a pattern that is used to perform a pattern match to identify a particular group of one or more source class identifiers associated with that regular expression that each correspond to a source class name of a source class, and wherein the source class filter module further comprises: a second source class fetcher comprising: a regular expression processor configured to receive the regular expressions input by the user of the user system; and a query builder configured to: generate and send a query associated with each regular expression to the interface, wherein the interface is configured to receive each query, contact the data store and find matching source class names for each regular expression, and return a source class identifier for each of the matching source class names to the query builder, and wherein the query builder is further configured to receive the source class identifiers for each of the matching source class names, and group the source class identifiers corresponding to each of the regular expressions into a second source class identifier array. 7 . The system according to claim 6 , wherein the application is a multi-tenant application, and wherein the user selects the one or more regular expressions to specify the particular group of one or more source class names corresponding to source classes that are of interest to a sub-tenant of the multi-tenant application during code coverage computations, and wherein the source classes associated with the particular group of one or more source class names collectively correspond to particular source code of the multi-tenant application that is of interest to the sub-tenant of multi-tenant application. 8 . The system according to claim 6 , wherein the source class filter module further comprises: a unique class ID filter configured to: receive the first source class identifier array and the second source class identifier array; and filter the source class identifiers from the first source class identifier array and the source class identifiers from the second source class identifier array to generate the unique source class identifier array of filtered source class identifiers by: combining the source class identifiers from the first source class identifier array and the source class identifiers from the second source class identifier array into a combined set of source class identifiers; determining duplicate source class identifiers that are in the combined set; determining invalid source class identifiers that are in the combined set; and eliminating the duplicate source class identifiers and the invalid source class identifiers from the combined set to generate the unique source class identifier array of filtered source class identifiers that correspond to the particular subset of source classes that the targeted code coverage metrics are to be computed for during code coverage computations. 9 . The system according to claim 8 , wherein the unique source class identifier array of filtered source class identifiers correspond to: a particular subset of all possible source classes that correspond to a particular subset of source code of the application that is of interest to the user and that the targeted code coverage metrics are to be computed for during code coverage computations. 10 . The system according to claim 9 , wherein the application is a multi-tenant application, wherein the user is a sub-tenant of the multi-tenant application, and wherein the unique source class identifier array of filtered source class identifiers correspond to: a subset of all possible source classes that are of interest to the sub-tenant during the code coverage computations, and wherein the subset of all possible source classes corresponds to a particular subset of source code of the multi-tenant application that is of interest to the sub-tenant during the code coverage computations. 11 . The system according to claim 7 , wherein the memory is further configured to store: a tooling API invoker and an OAuth generator executable by the processing system, wherein the tooling API i
using software metrics · CPC title
for coverage analysis · CPC title
for test results analysis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.