The Tsert Process ©® (patent pending)

The testing life cycle supported by the Integrated Testing Environment ITE that is Tsert is a simple one. The following steps are included:

• Use the Tsert-Planner to write a requirement document for the system to be tested. The requirement document can be the user manual or reference manual, etc.
• Use the Tsert-Planner to write a test plan, but first use the Tsert-Browser to setup a structure for the testsuite to be developed. The structure should correspond to the set of functionalities to be tested. Once completed, import the testsuite into the test-plan.
• Use the Tsert-Browser to write test scripts for the newly created testsuite.
• Each section in the requirements document is expected to have an associated keyword. It is these keywords that you are supposed to use when making a reference to a requirement in the test scripts.
• The Tsert-Engine is used to syntax check and execute the test scripts. This is an iterative process; errors will be discovered, as the scripts are developed.
• Once complete, assign a version to the testsuite and move it to the repository.
• Execute an official run, to establish a base-line for the Tsert-Tracker. The default tracking database now contains some relevant information.
• The keywords are traced and logged by the tracking database when the testsuite is run in official mode using the Tsert-Engine
• The Tsert-Engine automatically updates the tracking database with information for the official run.
• The default tracking database is used to track and update problem reports, when they are found.
• If changes are made to the application, then update the relevant test scripts in the testsuite and repeat this process from the beginning. The relevant system test plan and requirement documents need to be updated.