A lesson I learned from working in many projects as a tester or testing team leader is to focus on the quality of testing rather than the quantity of testing. It is a big mistake to measure testing effort and whether testing is good or bad by looking only to the number of test cases, number of issues found, number of testing hours or number of testers. Consider the following scenarios:
- Writing too many but incorrect test cases.
- Missing many valid issues.
- Overwork testing team all days and nights (including weekends).
- Involving all project team in test conduction (even non testers).
All the above scenarios are about quantity. Therefore, they will not lead to a high quality software. However, what if we focus on quality in each scenario to become like this:
- Writing less number but correct test cases.
- Finding valid issues.
- Giving testers the rest they need.
- Involving only testers in test conduction.
Sure the above quality scenarios are much more beneficial and will lead into developing high quality software.
All the best…