Overview

The DA Device Item service is used to represent the functionality of the Device. Each Functional Item implements some Functional Item Object Class interface. There are sets of predefined Device Items.

The Item Validator is used to test items against configurable input from JSON files.

Each physical device contains part of these items - Device Items and other protocol-specific items.

Device validation includes:

• Device name
• Device tags
• Device attributes
• Device status
• Set of device items

Device item validation includes:

• Set properties
• Get properties
• Invoke operation and assert the result and produced events
• device items are manipulated via user interaction and assert produced events

Adapters ⁄ Drivers ⁄ Peripherals logic includes:

• Adapter and driver restart, enable and disable peripherals applicable for ZigBee and ZWave protocols.
• When the adapter/driver stops, all devices become offline.
• When the adapter/driver starts, it is checked if:
  • all devices are online and operable
  • all setting values are returned correctly
  • all invoked operations have generated a correct event

Structure description:

• The main test scenarios related to DA Items and the automated test can be found in com.prosyst.mbs.test.templates.
• All device and protocol-specific items configurations are allocated in their respective projects. For example the Z-Wave test files are in DeviceConfigs and ItemConfigs folders in the com.prosyst.mbs.zwave/assemblies/testcases/src/main/resources/tee/sa/configs/com.prosyst.mbs.test.templates.device.items directory.
• The other protocol-specific projects – Bluetooth, Onvif, ZigBee, have the same analogous structure.
• All configuration resources are collected in runtime-validator.