Skip to content
This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
Viktor Petersson edited this page May 22, 2019 · 3 revisions

After each sprint, we need to do a QA run to ensure everything is working as expected.

QA Sign-offs

Please annotate here after each QA run

Date Sprint Name Comment

Pre-requisites

  • A Raspberry Pi with a fresh installation of Raspbian
    • Don't change the default password
  • A WoTT Dashboard account

Install the wott-agent

Follow the steps outlined here.

Claim the device

Follow the steps in the post-installation instructions from the agent to claim the device.

Ensure the device data

Ensure that the following data shows up under the device profile:

  • Device ID
  • Trust Score
  • Hardware Type
  • Last Ping/Heartbeat
  • Comment
  • Operating System
  • Operating System Version
  • Firewall Enabled
  • Open Ports
  • Download Certificate
  • Default password used
  • Certificate Expires
  • Hostname
  • FQDN
  • IP
  • SELinux Enabled
  • AppArmor enabled
  • Firewall rules

Verify that the default password is reported

  • Since we never changed the default password, that should show up in the dashboard for the device. Verify this.
  • After you've verified that the default password is reported, change the password on the device
  • Wait for the dashboard to pick up the change and verify that:
    • The default password no longer is reported
    • The Trust Score is changed

Verify port blocking works

  • On the Raspberry Pi, install nginx (apt-get install nginx)
  • Verify that you can access the webserver from your workstation (curl http://${IP})
  • Verify that you can see port 80 as open under the device security page
  • From the dashboard, select port 80 and 'Block' it
  • Verify that you can no longer curl port 80 on the device
  • Remove the block, and ensure that the connection is restored