Code Coverage vs Test Coverage; Subjectivity and Usefulness

It's really surprising how many people believe that code coverage and test coverage are the same thing. I don't know where this confusion has stemmed from, but from scouring around the internet, it seems to be a common challenge that people switch between code coverage and test coverage interchangeably, probably subconsciously too. They are not [...]

#NoTesting?? Here’s what it means to me.

The #NoTesting hashtag is having a bit of a resurgence recently, so I thought I would jump on the bandwagon and write down my opinions on the whole thing. The term is very confusing to say the least. Many people take it to mean "don't do any testing", which is understandable that they interpret it [...]

A Better Testing Pyramid

The Automation Triangle (or pyramid) has continually caused a bit of a stir in the testing world. It has been mislabelled many times to be called a "testing" triangle. It has been abused in many companies by being followed as a "test strategy". It has been butchered in ways that cause further misunderstandings and has [...]

“Start off with a turd and then polish it” – Really??!!?!

One of the most interesting discussions in the Agile community at the moment is about "MVP". I recently had a conversation with various community members and I heard someone say that MVP should be thought os as "starting off with a turd and then polish it"... It was another one of those times where I felt like I [...]

A Real(ly Questionable) ISTQB Question…

So... Another blog post stemmed from the depths of the LinkedIn forums. This time someone was asking for advice about answering an ISTQB exam question. The question is as follows (with this exact wording): If you are flying with an economy ticket, there is a possibility that you may get upgraded to business class, especially if [...]

Dispelling the misconceptions #6 – “Let it fail! As long as we fail fast!”

There has been lots of discussions about "failing fast" and how it's really good and we should all be aiming for this, but I think this is stemming a massive misconception... But I'm going to try to keep this post quite short. If we fail, then yes, I think failing fast is a pretty good idea. It [...]

Dispelling the misconceptions #5 – “Lets 100% automate everything and get rid of all our testers”

I hear this all the time. Even from very senior people. The latest one was from a development manager, asking why we "still need to have testers testing the software, since we are aiming for 100% automating for everything"... Firstly, the truth is very simple: YOU CAN ONLY AUTOMATE WHAT YOU KNOW AND EXPECT. When we [...]