Plan Duration
When estimating the execution time of test plans, there are a few guidelines to take into consideration to improve planning, resource allocation, and optimization of testing efforts.
Don’t Use Buffers
When estimating the execution time for test cases, it is important to represent the net execution time without any buffers. Historically, test cases may have included buffers, but it's essential to understand the current case you are working on and ensure that the estimation reflects test cases without buffers.
Break Down Activities
When estimating time for a test plan, break down the activities into the following components:
Setup: This includes activities such as reading through instructions and installing the build. Usually, 0.1 hours (6 minutes) is sufficient for this step, unless the instructions are lengthy or the build installation is complex.
Test Execution: This estimation comes directly from the included test cases, varying based on the complexity and scope of the test cases.
Potential Issue Reporting Time: The time taken to report potential issues depends on how broken or problematic the areas covered by the plan are expected to be. For this estimate, rely on historical experience and the testing focus. Avoid overestimating and be aware that testers can request more time when necessary. Avoid overspending client resources.
Teardown: This includes activities such as providing ratings, uninstalling the build, and cleaning up the device. Unless there are specific requirements, 0.05 to 0.1 hours (3 to 6 minutes) is usually sufficient for this step.
Adjust Duration As Needed
The execution time of the plan may need to be adjusted from run to run. For example, the first execution of a plan may require more time due to a larger number of issues found. Subsequent iterations may be shorter as issues are fixed or already reported.
Recommended and Maximum Duration
The recommended duration for a test plan is: 1.5 hours (90 minutes).
The maximum duration for a test plan is: 2 hours (120 minutes).
Based on existing data, these durations allow for an optimal balance between the number of issues reported per hour and the quality of tester results.
Reestimate for New Test Cases
Whenever new test cases are added to the plan, reestimate the execution time to account for the additional test cases and ensure the plan duration remains accurate.
Title
A test plan’s title should be relevant and specific and clearly convey which functionalities or features are covered. For example, the title could mention the specific functionalities being tested, such as “Admin Functionality Testing” or “Consumer Persona Testing”.
When you use an appropriate title, stakeholders reviewing the test plan can get a sense of the plan’s purpose at a glance.
Description
You can optionally use a test plan’s description to provide additional information about the testing purpose. While the main testing purpose should be evident within the test cases, the description can include details about any very specific purpose for the plan or any additional context. For instance, if there are specific personas (such as admins or consumers) that need to be tested, mention that information in the description.
It's important to keep the description up to date. If the plan's objectives, scope, or requirements change, adjust the description accordingly. This ensures that testers and other stakeholders have the most accurate and current understanding of the plan.
What's Next
Other guidelines on composing test plans