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"

"Why?"

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

"Why?"

"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!







Comments

  1. custom writing service reviews7 October 2017 at 07:45

    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.

    ReplyDelete

Post a Comment

Popular posts from this blog

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 follow...
68 comments
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
14 comments
Read more

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!
15 comments
Read more