Testing is the last phase a system must go through before going live. However, due to time-to-market pressure, by the time tests should start, it's almost too late to have complete or understandable requirements, a testing environment in place or a sound test plan. This often raises several difficulties that lead to low software quality, over budget activities and dramatic delays.

Having the testing team working alongside the development team leads to the definition of better requirements, a clear vision on resources and more realistic testing plans.

Tests management process can be divided in two different main activities. Test plan design according to your requirements and test execution. These two activities must be managed in order to take go-live decisions with confidence.

Specify requirements

Requirements based testing. Create your own test cases based on your requirements. Start to define your own requirements and link your test cases design to your requirements.

Plan tests

Start to organize all the information by creating different test cases types.

Create a test plan based on the identifying requirements.

Trace your test cases from your requirements.

Execute tests

Create test procedures (of any type) and perform test procedure executions. Test procedures can be of any type (load or non-load).

Analyzing test procedure execution results

Analyze test procedure results by using available graphs and reports.

Track defects

Report issues detected in your application and track how repairs are progressing.