Recently, I found it necessary to enumerate my beliefs about testing. I thought it would be good to share them with you. I’m sure these will change over time, as they have changed to this point. I’d like to know your thoughts in the comments. Enjoy. ~Paul￼
What I believe about testing
Testing is a service.
My clients have the right to determine acceptable level of risk for their application.
My customers are: Developers, Product Owners, my clients’ Customers, Management, Operations, and other Testers.
My scope for improving quality is from door to door – wherever it is accepted.
The primary purpose of Testing is not to gate a deployment, but to support, enable and enhance it.
The most important thing I can do is give accurate, clear, fast, and concise information about the SUT.
It is rare that 100% code coverage is necessary.
In 80% of cases, pragmatic solutions outclass ideal solutions.
Quality targets can be defined and progress toward them measured.
Each project, team, and organization is unique.
Quality can not be tested into a product.
Not only is it possible to develop testable code, it is usually helpful.
Testable code is generally of higher quality.
I am not a proxy for the user.
Testing is a service with numerous positive outcomes.
[…] a recent post entitled “What I Believe About Testing” I wrote “It is rare that 100% code coverage is necessary”. This may have caught people off […]
[…] is an expansion of my Beliefs on Testing post. Please take a look and let me know your thoughts in the […]
[…] months ago I started writing down my beliefs about testing. One of those beliefs […]
[…] teams also get better test coverage and code coverage by supplementing testing efforts with test automation and eventually having a […]