Ancora Imparo (Michelangelo, age 87)

When not to Test

There are Reasons for Dropping Tests. Be Aware of the Reasons and the Associated Risks.

Testing is an integral part of any software development process. After an initial test run during development there is usually a repeated test procedure in place. Ideally, it is fully automated and runs on a regular schedule. However, the scope of these tests rarely covers 100% of all functionality. There are always some parts that are not tested. What are those parts? When should you stop testing? How do you identify the components, where testing might not be worth the cost?

Liked this article?

We have a lot more where that came from!
Join the subscribers who stay ahead of the pack.

By entering your email, you agree to our Terms of Service and Privacy Policy.