-
Notifications
You must be signed in to change notification settings - Fork 1
Test Conduction in Detail
ErgoTobi edited this page May 24, 2019
·
4 revisions
The following describes the functional process of the GUI interacting with external systems within in the code.
- The lifecylce hook NgOnInit() starts readTestsetById() and receives the testsets incl. scenarios.
- A result based on the first scenario is produced.
- The GUI connects to the MQTT server and subscribes the data.
- The recurring part begins as per the set runQunatity attribute. A run based on the first scenario is produced.
- The test enviroment starts. As soon as the S/A VM is started, SpeedDreams begins and publishes data to the MQTT server.
- A buffer starts that sends 200 runDetails attributes with RunDetailBulk() in 1.5 seconds frequency.
- The fault injection happens according to the predefined time and QEMU Config JSON.
- A timeout stops the run, checks the state and running windows get closed.
- The lifecylce hook NgOnDestroy() ends the test and stops all subscriptions. The user is led to the Result screen.