The goal of the acceptance test is to verify and ensure the complete functionality of a client subscribed to TENS. The test is divided into two stages – a simulation stage, and a live stage.
The purpose of the simulation stage is to ensure that all of the functionality is working. This includes any customer post processing and system integration of the TENS notifications. The simulation stage, gives the customer the ability to trade and test functionality for an extended period of time, without risk.
When the end-to-end functionality is tested complete on the simulation system, it safe to go to the live stage. As it is currently not possible to test funding on the simulation system, we suggest that the customer prepare a small funding test to be executed on the live system.

Functional Testing

The table below describes how to generate the four types of notifications delivered by TENS. Please note that initial testing and tuning should be performed on the simulation system, as this is free of risks and costs.

Connectivity Testing

For every delivery method, it's important to ensure that the communication is failsafe and able to withstand network and system outages. If possible we suggest exercising the chosen delivery system by making trades on the platform, while the local delivery system is made unavailable. Make the delivery system available again, and confirm that the test did not result in any loss of notifications.