To learn how to implement your test routine according to one of the following test strategies:
Control-flow-based testing
You implement your test routine by specifying the routine's control flow. This is the same strategy as used for the previous example tasks.
Signal-based testing
You implement your test routine by configuring a standardized test scenario via the involved signals.
This is the first task in this tutorial that accesses your platform. If you use dSPACE real-time hardware, it must be installed and connected to your host PC. If you use VEOS, VEOS must be installed and running on your host or a connected PC.
Your task is to automate the downloading of a simulation application that represents a turn signal control in a car.
When the simulation is started, the battery voltage has to be set. Then the turn lever is switched to the right for a specified amount of time and back again.
During this scenario, the state of the front lights is captured.
A report of the test is to be generated that shows plots of how the involved simulator variables changed during the test.
When you work with the signal-based test strategy, you also automate the evaluation of the captured data. At the end of the test AutomationDesk checks, whether the captured signals comply with specified reference signals. Depending on that, a verdict is generated whether the test is passed or failed.
You can complete the task in two alternative ways by working through one of the following lessons:
Lesson 7: Control-Flow-Based Testing on a Simulation Platform
You will implement your test routine in a sequence that represents the routine's control flow and accesses your platform via automation blocks of the XIL API Convenience library.
Lesson 8: Signal-Based Testing on a Simulation Platform
You will implement your test as an instance of a sequence template that is provided by the Signal-Based Testing library. This sequence implements a standardized test scenario that is configured via the description of the signals which are used for stimulating and capturing the simulator variables during the test. You can also specify references for the captured signals and evaluate the test result.