Lightweight software test library for vehicle compute hardware coverage testing
US-12124356-B2 · Oct 22, 2024 · US
US9201764B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9201764-B2 |
| Application number | US-201313937691-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 9, 2013 |
| Priority date | Jul 10, 2012 |
| Publication date | Dec 1, 2015 |
| Grant date | Dec 1, 2015 |
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 development device and a method for creating and testing a control unit program, whereby the preparation of an intervention point for manipulating a quantity of a runtime environment for testing a control unit program component in a test environment having a test scenario program component and an observation device for receiving output values and indicating the test result. An executable program containing all program components is created from one or more program components, including a control unit program component that is to be tested and a test scenario program component. The creation includes generation of a runtime environment, wherein the runtime environment provides a communication channel for transmitting input and output values between the program components, and wherein a component test service is provided that offers an interface to the runtime environment pursuant to the AUTOSAR standard as an intervention point for manipulating a quantity of the runtime environment.
Opening claim text (preview).
What is claimed is: 1. A method for providing an intervention point for manipulating a quantity of a runtime environment for testing a control unit program component that is to be tested in a test environment having a test scenario program component for providing input quantities and having an observation device for receiving output values and indicating the test result, the method comprising: providing the control unit program component whose interfaces are each defined pursuant to the AUTOSAR standard; creating an executable program of the control unit program component to be tested and of the test scenario program component; generating the runtime environment, wherein the runtime environment provides a communication channel for transmitting the input and output values; providing a component test service that offers an interface to the runtime environment pursuant to the AUTOSAR standard as an intervention point for manipulating the quantity of the runtime environment and permits access to the quantity of the runtime environment by test scenario program components via suitable code generation for the runtime environment, the quantity determining or describing or influencing a communication process running over the communication channel; and executing the executable program, wherein an intervention in the communication process that is predetermined by the test scenario program component takes place via a manipulation of the quantity of the runtime environment through the intervention point, and executing the executable program, wherein an invention in the communication process that is predetermined by the test scenario program component takes place via a manipulation of the quantity of the runtime environment through the intervention point, and wherein a reaction of the control unit program component to the manipulation of the communication process between the program components is tested in that the reaction of the control unit program component is acquired by the observation device. 2. The method according to claim 1 , wherein the observation device is an observation program component whose interfaces are each defined pursuant to the AUTOSAR standard. 3. The method according to claim 1 , wherein the quantity of the runtime environment is specified by a parameter, a variable, or a function of the runtime environment. 4. The method according to claim 1 , wherein the quantity of the runtime environment is a status parameter that describes the status of an input or output value, and wherein the status describes the validity or the trustworthiness or an error type of the input or output value. 5. The method according to claim 1 , wherein the quantity of the runtime environment is a runtime environment event parameter that makes possible the triggering of a runtime environment event. 6. The method according to claim 1 , wherein the access to the quantity of the runtime environment comprises: manipulating the quantity of the runtime environment that is used by one function or by several functions of the same program component or by different program components. 7. The method according to claim 1 , wherein access to a quantity of the runtime environment comprises substantially simultaneous access to multiple quantities of the runtime environment. 8. The method according to claim 1 , wherein the control unit program component and the test scenario program component are located on a virtual electronic control unit, or wherein the control unit program component is located on a first virtual electronic control unit and the test scenario program component is located on a second virtual electronic control unit. 9. The method according to claim 1 , wherein the test scenario program component additionally determines a point in time and/or a range of validity in the program flow at which the predetermined intervention in the communication process is to take place. 10. The method according to claim 1 , wherein the executable program comprises: switching on and off the predetermined intervention in the communication process by the test scenario component. 11. A development device for providing an intervention point for manipulating a quantity of a runtime environment for testing a control unit program component to be tested in a test environment having a test scenario program component for providing input values and an observation device for receiving output values and indicating the test result, the device includes a hardware memory comprising: an electronic computing unit that is configured to generate an executable program from the control unit program component to be tested whose interfaces are defined pursuant to the AUTOSAR standard and from the test scenario program component, wherein the electronic computing unit is also configured to generate a runtime environment, the runtime environment providing a communication channel for transmitting input and output values, wherein the electronic computing unit is configured to provide a component test service that offers an interface to the runtime environment pursuant to the AUTOSAR standard as an intervention point for manipulating the quantity of the runtime environment, and permits access to the quantity of the runtime environment by the test scenario program component via suitable code generation for the runtime environment, the quantity determining or describing or influencing a communication process running over the communication channel, and wherein the electronic computing unit is configured to executing the executable program, wherein an intervention in the communication process that is predetermined by the test scenario program component takes place via a manipulation of the quantity of the runtime environment through the intervention point, and wherein a reaction of the control unit program component to the manipulation of the communication process between the program components is tested in that the reaction of the control unit program component is acquired by the observation device.
for test execution, e.g. scheduling of test suites · CPC title
by instrumenting at runtime · CPC title
Environments for analysis, debugging or testing of software · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.