Do small projects need extensive testing?
by Nataliia Vasylyna | August 12, 2011 10:00 am
Well, in this case you should think over the influence of project defects, not the scope of the project.
Nevertheless, if extensive testing is still not justified, risk analysis is needed.
Software testers might then do ad hoc testing[1], or write up a limited test plan based on the risk analysis.
What if There Isn’t Enough Time for Painstaking Testing?
You should use risk analysis to determine for what software testing should pay attention.
As it’s seldom possible to test every probable point of an application, every dependency, every probable complex of incidents, or everything that could go incorrect, risk analysis is appropriate to most software development projects. This demands experience, judgment skills, common sense.
Learn more from QATestLab
Related Posts:
- ad hoc testing: https://qatestlab.com/resources/knowledge-center/ad-hoc-testing/
- Black Box Test Techniques. Random Testing: https://blog.qatestlab.com/2011/09/19/black-box-test-techniques-random-testing/
- Useful Tips for Choosing a Test Automation Tool: https://blog.qatestlab.com/2011/06/08/useful-tips-for-choosing-a-test-automation-tool/
- Myths and Facts: Purpose of Software Testing: https://blog.qatestlab.com/2011/05/06/myths-and-rakes-the-purpose-of-testing-is-to-find-errors/
Source URL: https://blog.qatestlab.com/2011/08/12/what-if-the-project-is-not-big-enough-to-justify-extensive-testing/