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”
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” (Cem Kaner, Brett PettiChord et.al)
3: Stakeholders – in the broadest sense: developers, customers, users,…
7 thoughts on “So Everything Must Be Tested?”
[…] See also: So everything must be tested […]
[…] So Everything Must Be Tested? […]
[…] James B & Michael B. Thanks! 2 with specific permission from James Bach. 3 also referenced in So Everything Must Be Tested? Share this:Like this:LikeBe the first to like this […]
[…] this model the difference between a guru and an expert is – that the expert thinks he knows everything, while the guru knows he knows nothing. Even this model falls to the relative rule about X. If […]
[…] never have time to test everything. So in the context of classic test techniques and testing types (I’m looking at you, old […]