What Information Should a Test Specification Provide?
As a rule, careful preparations are made before proceeding to any mobile testing, desktop testing, web site testing. The preparations include creation of the test specification, allocating the resources, making ready the needed test data.
A test specification is a document determining what functions and features of the software are to be tested during the test procedure, in what way, how often they must be verified, etc.
All the project test specifications are included in the test plan.
A Test Specification Consists Of:
- general information about the testing procedure, namely the author of the document, the dates of it creation and updating;
- description of areas, aspects, functions and features that are to be checked;
- software aspects, functions and features that will not be verified during this procedure;
- test cases that are to be carried out;
- test cases that are run on every new build;
- description of security testing, functional testing, accessibility testing, performance testing that are included in the procedure;
- tests verifying whether the application complies with local and/or international requirements.
Properly written and detailed test specification is a basis of effective software testing. It helps the test engineers to understand the project, its weak and strong points and give the right recommendations on what should be changed in order to improve the application quality.