Posted by Ben Simo
For those that put faith in code coverage metrics:
Consider this: If a small change made to the code produces no change in the results of any of the tests, we have evidence of insufficiency of the full set [of tests].
- Robert H. Dunn,
Software Quality: Concepts and Plans
I am a tester, a skeptic, a defensive pessimist. This blog contains some deep thoughts, some half-baked ideas, and some rambling sentiments. (I'll let you decide which is which.) Whether you agree or disagree with me: you are invited to participate via the blog comments or email.
My opinions may not reflect those of my employer.
Have a question or topic you'd like to see addressed here? Please contact me.
follow me on Twitter
1. The value of any practice depends on its context.
2. There are good practices in context, but there are no best practices.
3. People, working together, are the most important part of any project's context.
4. Projects unfold over time in ways that are often not predictable.
5. The product is a solution. If the problem isn't solved, the product doesn't work.
6. Good software testing is a challenging intellectual process.
7. Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.
0 Comments:
Post a Comment