|
| Test | Expected result | Result | Remarks |
|
| Start with the hub, and OpenHAB service configuration is running on the hub without an Internet connection | Initialize the database connection, start OpenHAB service, and connect to cloud service if available. Establish a connection with the MQTT server and update device states | Successful | Start-up takes about 45 seconds on average (out of 20) to start up Raspberry Pi and OpenHAB service |
| Connect a LAN or WAN to the hub while OpenHAB service configuration is running | Trigger cloud connects service to establish a connection with the cloud server and sync device states | Successful | Cloud service worker detects Internet connectivity, and cloud loads configurations with a connection 10 seconds |
| Stop the OpenHAB hardware application or power off Raspberry Pi while OpenHAB service is still running | Raise ForcedTermination event in OpenHAB Control Panel logs and publish to ForcedExceptions MQTT topic | Failed some of the time | Failed some of the time. The cause is a delay in publishing before power is cut |
| Create a new “Home” location in the OpenHAB Control Panel | The location should be added to the local database and posted to and made available on the OpenHAB server | Successful | A new location is immediately available |
| Add a new appliance in the OpenHAB Control Panel | The appliance with its properties should be added to the local database with OpenHAB service refreshed to show the update as well as send push notification to registered users | Successful | A new appliance was immediately available. The push notifications, however, worked 99% of the time |
| System vulnerability test | No breaches or vulnerabilities during test runs locally at the client as well as remotely | | Firewall bypass testing was a success.The system withstood DNS-level attacks, e.g., switching and routing tests |
|
