We all know that it is impossible to perform exhausted testing in practice even with a small software application. The reason is that we have limited schedule time and budget while the number of tests is almost unlimited. The art of software testing is to find a right balance that maximizes the outcome of testing within a given schedule time, budget and other constraints.
In this post, we will discuss a method that helps find such a right balance.
But at first, let’s consider a few common scenarios that you as a tester may encounter. One scenario is that you have 1,000 test cases to be written and tested for a one-month iteration or sprint. Your project produces many builds during the iteration. And your testing team has 3 people, which is barely enough for testing every test case once. Because your manpower is limited, you have to decide which test cases to test for which build and which test cases have to be tested repeatedly on multiple builds. For another scenario, in a later stage of the project, your customer requests to test a build to release, and you have only 5 days to test 2,000 test cases. What would you do if you don’t have enough manpower to test all of the test cases in 5 days?