Skip to content

Integration Testing

Matej Sychra edited this page Nov 10, 2017 · 2 revisions

Logo

THiNX Integration Testing

Networking environment

You should setup your own separate network in order to avoid network setup changes on location changes.

WiFi SSID: THiNX-IoT

Password: <enter-your-ssid-password>

Reserved identifiers

There are certain identifiers used for testing. E.g. newly registered device created on test should be destroyed by the very same test in order not to clutter the database.

There are some registered identifiers for keys, devices and users, that should not be deleted, as they are used for continuous testing and integration.

Build Tests

  • GIT Repositories for PIO, Lua, INO, UPY and MOS firmwares/builders

User Activation Test

  • Test user must not be rejected when already exists (previous tests or deletion may have failed)

  • Test user receives the activation directly in response, instead of having to wait for an e-mail.

User Password Reset Test

  • Test user receives the reset_key directly in response, instead of having to wait for an e-mail.

User Revocation Test

  • Test user must be deleted after any tests are performed; even on failure.

Device Registration Test

  • New device is given new UDID that it MUST honor and save. Device without UDID should be checked for MAC address and if found, treated as existing device (see Device Checkin).

Device Checkin Test

  • Existing device is considered the one with UDID set to anything valid from device side.
  • Device may be offered an update in this point.

Device Update Test

Device may request an update:

  1. firmware
  2. files

Device Migration Tests

USER PASS MAIL OID
test **** syxra(@)syxra cedc16bb6bb06daaa3ff6d30666d91aacd6e3efbf9abbc151b4dcade59af7c12
cimrman **** cimrman(@)thinx 4f1122fa074af4dabab76a5205474882c82de33f50ecd962d25d3628cd0603be

Testing Exceptions

  • User activation: The username test will not receive error when already exists.

  • User activation: The e-mail cimrman@thinx.cloud will not receive error when already exists.

  • User activation: The username test will receive the activation key in response, instead of having to wait for an e-mail.

  • Password reset: The username test will receive the reset key in response, instead of having to wait for an e-mail.

Test Devices

Wemos D1 Mini 2.1.0

  • Test Periperals: LPWAN SigFox Node, Telekom Design TD1208 SigFox

Wemos D1 Mini 2.2.0 EAV

Robotdyn D1 Mini 16m

Robotdyn WiFi-NodeM 32m

Robotdyn Mega-WiFi

Robotdyn Mega-WiFi

Currently Unsupported Devices (on Roadmap)

ESP32 WROOM

Heltec HTPT-WB32LA (LoRa)