Reviewing some techniques for test case analysis
If you were to ask different experts to categorize test cases by their priority, you would likely come across very different opinions. This task is not trivial, as having the right categorization could help us identify which test cases to automate first, or which ones to execute on our build verification tests (BVTs) so that we could promptly find the maximum number of issues and identify the most important tests cases that would cover them.
Most of the audience members I have asked throughout several conferences affirm to have more than 100 and even up to 500 test cases to explore per deployment or to automate. Handling so many test cases per deployment is currently achievable thanks to cloud parallel testing platforms (more on that will be covered in Chapter 9, Having Your Head up in the Clouds). However, these tools might charge us money per run or per the number of tests executed, and we must ensure those tests are bringing value...
