In my last post, I talked about how I presented a set of individual quantitative reports to some management figures to illustrate how they could be misleading and why it was necessary to understand the story behind the numbers rather than simply place value on the numbers themselves. After I had led them successfully up…
Quantitative vs Qualitative Reporting (Part 1)
I used to work in structured environments for many years where in the field of (test) reporting, numbers were definitely king. The upper echelons of the management team demanded a quantitative style report and that’s what I delivered. I had suggested that an alternative style of reporting would be beneficial so that they could actually…
Battling the Bias
There seems to be a particular word that crops up again and again in blogs, papers and presentations about software testing and beyond: Bias Honestly, it’s everywhere. Some examples: Observational Bias (Darren McMillan, Requirements Analysis & Testing Traps) Darren quite rightly points out the dangers of having visual references (wireframes) at a very early stage…
One Line Change
In my experience over the years, I’ve heard one phrase consistently used by developers across different organisations in order to try and mitigate risk associated with any one or more deliverables due for test team. These particular deliverables tend to be for specific issues such as a critical bug that needs to be addressed in…
Software Testing ShuHaRi
As a martial arts practitioner for over 25 years, there’s been a concept I’ve been aware of for a long time that could be easily be loosely applied to software testers making a transition into the world of exploratory testing from what we may refer to as ‘traditional’ testing (dare I say, ISTQB :-)). This…
Finding Deefex 