Service tab¶

The Service tab is only shown if at least one network description file containing service descriptions has been registered on Bus access tab of the test configuration or a service port is chosen there. It displays the service related information from the network description file(s) (e.g. control units, services, methods, fields and events) in a tree view.

The parameters and return values of the methods and events are often complex values like structures or arrays. These can be expanded further to gain access to the scalar leaf nodes and substructures.

Use the service tab to create and insert service related test steps into test cases. To make this work, it is necessary to assign a service port (i.e. a tool providing service access, see ETHERNET) in the test configuration (Bus access tab).

Info

Use shortcut <CTRL>-<F> to search and make methods visible in the tree view.

Important

Event registration with the service tool(s) as well as the start of acquisition request(s) are performed during the pre-processing stage of test execution. It happens in the background and can take several seconds. That is why events might not have been received yet immediately at test start. If this is an issue, one can insert a Wait test step at an appropriate position in the test case, or parameterize the read test step with Wait until true and possible expectation ~Present~.

Test steps¶

Execute method: Drag method items to your test case in order to create test steps that invoke service methods on remote control units. If the called method has a return value and the checkbox Ignore response is not checked, test step execution blocks until the return value is obtained. When using certain E2E structures, as denoted by the description, the values can be filled automatically. In order for that to happen, a placeholder value needs to be specified in the test bench configuration, and this value must be assigned to all E2E structure members here. Supported profiles are 4, 7 and 11. Parameterization is done with the Execute dialog.
Read method parameter: Right-click method items in order to create test steps that read the parameter values from function calls made by arbitrary participants of the communication. Parameterization is done with the Execute dialog.
Read method return: Right-click method items in order to create test steps that read the return values from function calls made by arbitrary participants of the communication. Parameterization is done with the Execute dialog.
Read event: Drag event items to your test case in order to create test steps that retrieve and store the most recent value received for the event. Parameterization is done with the Execute dialog.
Send event: Right-click event items in order to create test steps that send the event. Automatic filling of E2E structures is possible, analogous to Execute method. Parameterization is done with the Execute dialog. Send cyclic allows to periodically send the event in parallel to the test case execution using the given cycle time. Send event and Service-Simulation can be used simultaneously if different services are provided and the IP addresses are different.
Provide method: Right-click method items in order to create test steps that provide the method for other participants to call it. Automatic filling of E2E structures is possible, analogous to Execute method. Parameterization is done with the Execute dialog. For the setting of return values call parameters of the method can be used via the keyword RequestParams and the dot notation. All values that are not call parameters are applied at test case execution time. Provide method and Service-Simulation can be used simultaneously if different services are provided and the IP addresses are different.
Read or write leaf nodes: By dragging or right-clicking leaf nodes of events and methods, you can create test steps that read the return values and parameters of function calls and events from other parties’ communication, or provide new values to an external restbus simulation. Parameterization is done with the Read / write dialog.
Suspend or resume offering the service: Rigth-click service items in order to create test steps that suspend or resume offering this service. This test step works for services that have at least one simulated method or event.

Important

Depending on what tool, what port type, and (if applicable) what TCP/IP stack is used to access services, only a subset of these test steps is supported.

See also the explanation of the different Ethernet port types.

	SERVICE [LwIP]	SERVICE [System]	SERVICE-(PCAP-)PASSIVE	SERVICE_MANAGER
Exectue method
Offer method
Read method parameters / return values
Read event
Read event leaf
Write event leaf
Send event
Suspend or resume / offering the service

Structures¶

Parameterization of these test steps frequently requires complex values like structures or arrays. Such complex values can be created by use of variables of type Structure. The easiest way to create an appropriate structure variable is to drag the parameter or return value from the Service tab to the Variable window.

Trace analysis¶

Events, methods, and their leaf nodes are also available as trace signals. They are currently supported with the PCAP and BLF recording formats.

Generating service modules¶

The context menu of the service itself offers an option to generate a python module suitable for simulating the chosen service.