The list of the devices tested with the relevant items can be found in List of Devices.
Before a particular device is tested, do make sure there is a written configuration for it.
To skip a device – If a particular device is in the network, but you do not want to start it together with the rest from tee/sa/configs/com.prosyst.mbs.test.templates.device.items/DeviceConfigs directory, set the skipThisDevice property to true.
By default, all properties are set to false.
To run user interaction actions – Some configurations contain user interactions.
For example, the Bosch Motion Detector contains an item Detector that is motion-sensitive. It gets activated if someone waves a hand in front of it.
If this user motion is not performed, the test will fail. The reason for the failure is, that the test expects to receive an event PROPERTY_CHANGED and to change the Motion Detected property from false to true.
If you want to deactivate these interactions for the completion of the test, set to false the runUserInteracionActions property, which is located in tee/sa/configs/com.prosyst.mbs.test.templates.device.items/UserInteractions directory.
To enable the protocol for execution – set property com.prosyst.mbs.test.templates.device.items.<protocol>=true
To enable Event Generators – set property com.prosyst.mbs.device.items.enable.event.generators=true
Test execution
The automation test is executing through configured Jenkins jobs.
To execute the test manually:
Start the Bosch IoT Edge Services SDK.
Add the necessary devices to the network according to the specific description for each device.
or
Provide a backup with the devices and use its location as a value for the com.prosyst.mbs.device.items.backup.location property
Execute the test jar in the TEE group
Execute the test in Eclipse – Right-click on the project —> Test on —> Select OSGi Framework —> Add —> Enter your Framework' IP address —> Click OK
During test execution:
The test results can be found in tee/sa/logs/SystemProject directory.
Detailed information is displayed in the Framework's console as an output for better UX and traceability.
Make sure that Device configuration and Device item configuration are valid. Otherwise Incorrect JSON format warningappears in the output of the console upon starting the test.