Test Plan in software Testing |Definition , Activities etc
Test Plan is the most important activity undertaken by a test leader in any test project.
This article will present you with a complete idea about TestPlan , Test Activities , entry and exit criteria etc.
We will learn below topics in this article
What is Test Plan?
- It is the most important activity undertaken by a test leader in any test project.
- Ensures there is a list of tasks and milestones in a baseline plan to track progress .
- Defines overall testing objectives and approach
- Provides accurate test effort
Test Plan Activities
- Determine the scope and risks that need testing, involve the Project Manager
- Identify and agree on the objectives of testing, with a focus on TIME, QUALITY and COST.
- A Test Strategy (Overall Approach) ensures that test levels, entry criteria and exit criteria are defined
- Making decisions
- Features to test?
- What roles will perform the testing activities?
- When and how the testing activities should be done?
- How the test results will be evaluated?
- Exit criteria
- Create a Plan to identify when and who will undertake the test analysis and design activities along with the documentation of the schedule for test implementation, test execution and test evaluation
- Decide on the format of test project documentation, and which plans and test cases will be documented.
- Define Management information including the metrics required, establishing processes to monitor and control test preparation and execution along with defect resolution and risk issues.
- Ensure that test documentation generates test assets i.e. test cases.
- Defines when to start testing
- Can include the start of a level of testing, start of test design and/or start of test execution.
- The stages of Entry Criteria to Test Execution are as follows:
- Test tools installed in the environment which should be ready for use.
- Testable code is available.
- All test data is available and correct.
- All test design activity has completed.
- Exit Criteria is used to decide when a test activity has been completed or needs to stop.
- Exit Criteria can be defined for all test activities such as planning, specification and execution or for a specific test level for test specification and execution.
- Exit Criteria should have been agreed as early as possible in the life cycle.
Typical exit criteria are:
- Estimates of defect density or reliability measures
- Functionality or risk
- Thoroughness measures, such as coverage of code,
- Residual risks, such as defects not fixed or lack of test
IEEE-829 Test Plan
- TestPlan Identifier
- Test Items
- Software Risk Issues
- Features to be Tested
- Features not to be Tested
- Item Pass/Fail Criteria
- Suspension Criteria and Resumption
- Test Deliverables
- Remaining Test Tasks
- Environmental Needs
- Staffing and Training Needs
- Planning Risks and Contingencies
SPACE DIRT = IEEE829 TestPlan
S – Scope test items, what to test, what not to test
P – People training, responsibilities, schedule
A – Approach the approach that will be taken to testing
C – Criteria entry/exit criteria, suspension/resumption criteria
E – Environment test environment needs
D – Deliverables what is being delivered as part of the test
I – Incidentals introduction, identification (of the document),
R – Risks risks and contingencies
T – Tasks the test tasks that are involved in the testing