|
Section |
Mandatory/Optional |
Description |
0. Configuration |
Mandatory |
Title, Author, Version, Date. |
1. Introduction |
Mandatory |
A brief description of the domain/technique example, giving an overview of the problem to be solved and the approach taken. |
2. Requirements/Specification of System under Test |
Mandatory |
A description either as requirements or specification of the system under test (SUT), which this technique is being used on. |
3. Test Design |
Mandatory |
Definition of the test case design technique and how to apply it. |
4. Actual Test Cases |
Mandatory |
The test cases that are generated by applying the test design technique to the SUT. |
5. Implementation of Test Cases |
Optional |
A brief discussion about how the test cases would be implemented. This is optional and need only be included for techniques where implementation of the test cases is a factor e.g. performance/stress. |
6. Evaluation |
Optional |
How to analyse the results generated by implementing the test case. This section is optional and need only be included for techniques where evaluation of the results is a factor of their design e.g. performance/stress. |
7. Scope for Automation |
Optional |
An optional note, if required, about additional considerations when automating test cases designed using this technique. |
8. Conclusion/Summary |
Mandatory |
A conclusion/summary section for this domain/technique example. |