A checklist of tests to be performed before uplink is delivered to a customer

[de-sh]

NOTE: this should be treated as a living document and updated appropriately

• Does uplink connect to broker.
• On connection, does uplink subscribe to the appropriate topic: /tenants/<project_id>/devices/<device_id>/actions
• Does uplink send ping_req and receive ping_resp according to the keep_alive configuration.
• On network close, with simulator/data generator connected and uplink configured to write to persistence, does uplink write the data as publish packets to files for handling back-pressure.
• When there are exactly the limit(n) number of files as specified in config, does uplink delete the first file from the persistence directory and continue to write to n+1'th file.
• When there are files in persistence directory at startup, does uplink read and forward them appropriately, while writing incoming data onto disk and waiting for the reading to be completed before writing the incoming data directly to network.
• Is any file larger than the configured file size.
• When a stream is configured to contain n data points, does bridge wait for either the specified timeout period from receiving first data point or for n data points in the buffer to be breached.
• Can an application connect to uplink over TCP, receive the actions specified for it in the config and send data that is then batched and forwarded to platform.
• When a download action as configured is received, does uplink forward it to the download handler, does the download handler write it to the appropriate location in disk.
• Does uplink write loglines from the configured services with configured loglevel to the logs stream.
• On an action configured to be completed in 100s, with the action route timeout, does the bridge send a failure action response.
• Does uplink allow for it's tracing_subscriber minimum loglevel to be configured with a curl command when running as a daemon.
• Does uplink allow tunshell access for remote device control.
• Does uplink allow configured processes to be executed through an action remotely.
• When configured, does uplink write system stats to the appropriate streams, i.e. processor, disk, memory, etc.