...
End-to-end tests
Physical tests
Unit tests
Before any feature or bug fix is merged with the upcoming deployment branch, automated unit tests are executed. These test validate the workings of the feature, and compatibility with all network server components it interacts with.
End-to-end tests
Before any feature or bug fix is merged with the upcoming deployment branch, automated end-to-end tests are executed to test compatibility and regression. End-to-end tests are designed to mimic user behavior and to simulate different LoRaWAN scenarios. User behavior scenarios contain complete user stories that are critical to the overall integrity of the application and usually comprise multiple components and views (e.g. creating applications, registering gateways, changing device settings etc). The LoRaWAN end-to-end test validate compatibility and test regressions by simulating scenarios such as sending uplinks and downlinks and process join requests.
Physical tests
When end-to-end tests are completed, the new feature can be merged to the upcoming deployment branch. The release cycle starts with deploying The Things Stack, including its newly merged features to the staging environment. Only when the staging environment passes all physical tests, a release is planned for the production environment.
The Things Industries operates a physical test lab, containing multiple gateways and devices which continuously run LoRaWAN test loops. These test loops include:
Sending uplinks.
Receiving downlinks.
Testing operations mode class A and C.
Running through the join process for a Cluster Join Server and the Global Join Server.
Testing integrations using HTTP Webhooks, MQTT and Pub/Subs.
Exchanging traffic between different tenants within The Things Stack Cloud hosted, and between dedicated The Things Stack deployments using the Packet Broker.
All of these loops are tested using For the physical tests, gateways which run the UDP Packet Forwarder as well as LoRa Basics Station are used.
Section 3. Incident Management Process
...