My blog

My thoughts on all things quality & testing

Overthinking it (I can, therefore I will!)

10th Apr 2017

... as testers it's very easy for us to get carried away with our work, over-think the task at hand and produce *less value* to the long term project targets in favour of short term value to that single task.

Fore! How to score better with your testing approach

4th April 2017

... Do people in YOUR context regularly evaluate your testing tools and techniques to make suggestions on improvements or do you sit quietly and not question the status quo? As testers we should strive to read about tools, try tools out, make mental notes on how you might use those tools best in your daily testing work and then maybe leave the tool alone until the task at hand DEMANDS that tool!...

Accept misnomers

27th March 2017

... What we need to strive for is the establishment of a common 'language' on projects that allow the participants the ability to discuss things in the most efficient manner possible adding as little ambiguity into the discussion as possible, not to pick apart people's differing descriptions of the same thing.

NOT testing is powerful!

25th Nov 2016

As the conversation went on there were a lot of tests he described, that I found to be basically pointless, and it got me thinking about how as professional testers we automatically use our experience, knowledge and heuristics to decide on the best approach and best set of tests/checks to run - from applying every test known to man to no tests at all, with anything in between.

Do you like it dirty?

1st November 2016

... I completely see the benefit to all levels of dirtiness in testing setups but what I struggle with is lack of time on our many one hit waterfall projects and prioritising those levels of dirtiness in terms of time spent setting up versus bugs encountered versus time spent investigating and ruling out other system interactions as the cause etc....

Logical Reasoning

31st July 2016

... I completely see the benefit to all levels of dirtiness in testing setups but what I struggle with is lack of time on our many one hit waterfall projects and prioritising those levels of dirtiness in terms of time spent setting up versus bugs encountered versus time spent investigating and ruling out other system interactions as the cause etc....