Test plans can be created at two levels: the project one (master test plan) and at subsidiary levels (unit, integration, system, etc.). Despite of the level, test plan consists of several sections which have their own specific features and goal.
What Are the Constituents of Test Plan?
- Identifier (helps to distinguish test plan from any other document).
- Introduction (a brief summary of software).
- Test items (software elements that should be checked).
- Features (the characteristics that should be tested, for example, security, usability, load capacity, etc.). Besides the features to be checked, system features that should not be tested and the reason of that are defined in this section.
- Approach (the appropriate testing approach which will ensure the most effective and efficient performance of the checking procedure. For example, automated principle applied during web application testing or mobile testing.)
- Pass/fail criteria (the parameters according to which the test item is considered to pass or fail).
- Additional conditions (under which testing procedure may be resumed or suspended).
This particular list of constituent element of test plan is not full. There are sections which contain the information or parameters needed to conduct software product testing. The practice shows that the checking procedure cannot be performed without creating test plans.
- Stress, Performance and Load: Three Pillars to Lean On during Testing
- Software Testing: Complicated Burden or Elegant Endeavor?
- Simulating the Reality during Performance Testing
- Security Testing: Universal Recommendations and Techniques
- Security Testing: Protecting Customers from Day One