Aim 
During the Specification phase, the required tests and starting points are specified. The aim is to have as much as possible prepared, in order to be able to run the test as quickly as possible when the developers deliver the test object.

Method of operation
During the Specification phase, the testers specify the required tests per test unit. This is done by creating checklists or specifying test cases on the basis of the allocated test design techniques. In the latter case, the testers also create test scripts, in which the test cases are put into an efficiently executable sequence. On this basis, and partly in parallel with it, the testers define one or more central starting points for the testing that the test cases can use. This may be a copy of production or a central base table listing. A special form of a test to be specified is the test object intake. This test should check in the Execution phase whether the test object is sufficiently testable for a meaningful and efficient test execution.

Activities
Within the Specification phase, the following activities are distinguished:

1. Creating test specifications
2. Defining central starting point(s)
3. Specifying the test object intake.    

For more information on the activities in the Specification phase please check the TMap Next book.

Products 

• Test basis defects
• Test specifications (checklists, test cases, test scripts)
• Test basis defects
• A description of the central starting point(s)
• Checklist of test object intake test
• Pre-test test script    

Techniques 

• Test design techniques
• Checklists for various quality characteristics    

Tools 

• Testware management tool     
• Defect management tool 
• Test data tool         
• Test design tool     
• Model-based testing tool 
• Automated test execution tool         
• Performance, load and stress test tool