Everything? Really? A 100% Coverage(1) of everything? As in E-v-e-r-y-t-h-i-n-g? nah…
“Something must be tested” … oh wait (2) …
“Something – that matters to someone who matters – must be tested”.
So who matters – who decides what to test?
“Something – that matters to the stakeholders(3) of the project – must be tested”
Use both right and left brain parts (The Right Brain for the future) remember!
“Something – that matters to the stakeholders of the project – must be explored and confirmed” (4,5)
So what is this something that matters?
“A solution that solves a problem for the stakeholders – must be explored and confirmed“
Must? Always? MustShouldCanWould (MoSCoW) ? Everytime? OK OK
“A solution that solves a problem for the stakeholders will be explored and confirmed within a given business context“. In short –The scope of testing is a business decision
2: “A bug is something that matters to someone who matters .. to me” (Michael Bolton, James Bach, Cem Kaner, Brett PettiChord et.al)
3: Stakeholders – in the broadest sense: developers, customers, users,…
4: Michael Bolton http://www.developsense.com/blog/2009/08/testing-vs-checking/
- Checked as in confirming, using scripts and sequences
- Tested as in learning and exploring, sapience
5; Rapid Software Testing http://www.satisfice.com/rst.pdf pages 59-67.