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
Matt Heusser sent the context-driven-testing email group a series of questions about handling regression testing. Specifically he asked: How do your teams handle regression testing? That is, testing for features /after/ the ‘new feature’ testing is done. Do you exploratory test the system? Do you have a standard way to