A common problem is faced in testing phases (especially when UAT/release is near) – There are so many tests for testing/execution but there is so less time. In 2004, Johanna Rothman gives a recipe in her article “So Many Tests, So Little Time
| TimeBox the testing”. From Johanna’s article, I conclude that Prioritizing the tests is one important step to achieve time-boxing in testing.
For those who don’t know what is time-boxing:
Time-boxing is a well-established project management (time management technique) used to limit project scope in a fixed duration by forcing tradeoffs. Time-boxing is a valuable technique for testing as well. For example you need to test the application before UAT and there are only 4 weeks left.
Here we will discuss, how to prioritize tests (test scripts/test cases), complete the most important tests in given time and deliver a high quality product. There can be many other best practices for time-boxing the testing but Prioritizing the tests is one important step to achieve time-boxing in testing.
Why to Prioritize Tests:
| TimeBox the testing”. From Johanna’s article, I conclude that Prioritizing the tests is one important step to achieve time-boxing in testing.
For those who don’t know what is time-boxing:
Time-boxing is a well-established project management (time management technique) used to limit project scope in a fixed duration by forcing tradeoffs. Time-boxing is a valuable technique for testing as well. For example you need to test the application before UAT and there are only 4 weeks left.
Here we will discuss, how to prioritize tests (test scripts/test cases), complete the most important tests in given time and deliver a high quality product. There can be many other best practices for time-boxing the testing but Prioritizing the tests is one important step to achieve time-boxing in testing.
Why to Prioritize Tests:
- We can’t test everything.
- There is never enough time to do all testing you would like.
(Read Testing Limitations)
Tips to Prioritizing the tests:
- Possible ranking criteria ( all risk based)
- Test where a failure would be most serve (take help from development team)
- Test where failures would be most visible (take help from development team)
- Take the help of customer/Business Analyst in understanding what is most important to him.
- What is most critical to the customers business? (Take the help of customer/Business Analyst)
- Areas changed most often. (take help from development team)
- Areas with most problems in the past. (take help from development team)
- Most complex areas, or technically critical. (take help from development team, Business Analyst)
Note: If you follow above, whenever you stop testing, you have done the best testing in the time available.
yes, I do this in my day to day testing activity. Actually I have only 3 weeks of time for each prod release. I have to have prioritizing tests.