Skip to main content

Why? Why? Why? The questions of a 2 year old AND Testers!

Apologies for the lack of blog posts, but for those that don't know me, not only am I a struggling Tester, but also a struggling Parent! I have 2 kids, a 2 year old and a (soon to be) 5 year old! They are my world, and they're also the inspiration for some blog posts that I tend to write, this latest one is no different...

My 2 year old daughter has begun to question a lot of what I say to her.

"Please don't climb up the slide"


"Because the slide is slippery and you might hurt yourself"


"Because it rained last night"

Ad infinitum!

My 5 year old said to me and Jess the other day "We mustn't ask "Why?" must we because that is answering back" I thought to myself, I don't want him to stop asking Why? to stop asking "What If?" This is a massive skill and something we as Testers should definitely have and encouraged. So I had to explain to him that it's not a problem to ask "Why?" it isn't answering back, if you genuinely don't understand something, then you need to be able to ask "Why?" without fearing anything happening to them.

The last thing I would want to suppress, both in Testers at work and my children at home is the freedom and the environment in which they can ask questions and they can question anything without fear of being laughed at or being told off.

Sure there are times when the questioning becomes too much (especially from the kids!), or it's at an inappropriate time, but that applies to life in a Development team as well. You don't want to be questioning things at the very end of something, similar to finding bugs, the earlier you can ask questions the easier they are to answer and hopefully react upon.

I genuinely believe that there is no such thing as a "Stupid question" but also that sometimes the most silly questions are really good questions and can throw up some confusion around what is being developed. If we don't question things, then we won't improve and we'll stay the same!


  1. I agree with you many silly questions really have some positive impact plus some positive answers too. And I think the ones who do silly questions are the real intelligent people.


Post a Comment

Popular posts from this blog

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 

By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

        public static void AfterTestRun()
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))

        private s…