laboon / ebook

Software Testing ebook
159 stars 62 forks source link

Exploratory Testing and Safety-Critical Domains #88

Closed ewiancko closed 9 years ago

ewiancko commented 9 years ago

In the second-to-the-last paragraph of section 11.1 you say "If you are working in a safety-critical domain, or one in which there is the necessity of documenting what has been tested, relying on exploratory testing will not serve you well."

On my current project we are working under FDA regulations. (I think this is what you mean with the reference "safety-critical'.) And we do 'rely' on exploratory testing - just not solely on it. (We are actually required to do it every sprint in fact!)

Although it may not be intended, I think the impression is given that it can't or shouldn't be used in that setting. It may be better clarify - even if you just insert the word "solely" in the phrase: "relying solely on exploratory testing will not serve you well."

Exploratory testing is very important after all. In my albeit anecdotal experience anyway, exploratory testing yields 40% to 50% of actual the defects logged.