Does better testing always lead to better software? This article, “Four reasons to stop testing: Finding the right balance in software quality,” explores the places in which you might reasonably scale back your testing efforts, while keeping an eye on the pitfalls and risks of holes in your test coverage. In the end, it is always a delicate balance between cost and benefit, as well as a tradeoff between the short and long term.
What You’ll Learn:
- Which types of risks are mitigated by which type of tests
- How future plans for development impact current testing needs
- Where arguments against extensive testing are valid
- What risks you have to accept when saving on testing costs
After reading, share your thoughts:
- What criteria does your team use to decide when you have tested enough?
- Have you experienced situations where reducing testing seemed reasonable? How did you decide?