The functions to be tested A test specification can combine any of these formats, as needed. Proving that the software doesn't do what it shouldn't do Test cases can be organized in a variety of ways, depending on the size, type, and complexity of the software being tested. For example, tests can be organized by type of test, by product feature, or by a combination of the two. What went wrong. This section should be descriptive enough that the problem and its location are obvious.
Reproduction steps The detailed procedure for reproducing the bug.
This might include platform or installation details. Tracking data Who found the error, who's fixing it, and other pertinent data. This section contains a sample outline for each type of testing document. Test criteria Acceptance, pass, suspension of test criteria. Bug tracking Location of bug database, key bug data format.