Exploratory testing was first coined by Cem Kaner who defined it as a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually
I’ve come across a number of Frequently Asked Questions about Exploratory Testing and I’ve got what I hope are pretty good answers. Exploratory Testing FAQs Frequently Asked Questions about exploratory testing. Got a quick question? Get a quick answer. Yes, there are many examples where people have used
Since CAST 2015 I’ve wanted to implement an interesting idea that could potentially give my testing greater visibility and greater scrutiny: Putting exploratory testing charters into our project tracking tool. At work we use GitHub to host our code which means we use GitHub Issues as our bug tracker.
I was recently talking with someone about their testing strategy and process when I noticed they were trying to build overly-detailed test scripts (procedures). It didn’t take them long to realize specifying to such detail often left them bored (writing became redundant) and so each test became less and