Skip to main content

An intrinsic ability to test?

I've recently been off work for a little while (and will be for a few more weeks), and been able to spend a lot of time with my 2 year old son and my newly born daughter (hence the lack of posts!)

I've realised something over these past few days, that every child is born with a natural ability or an intrinsic ability to "test". Obviously I'm not talking about testing software :)

This is more about testing their surroundings, testing what they can and can not do with their toys and just testing themselves to see what they are truly capable of (that last one is definitely apt for my new born daughter!)

Unfortunately, I believe this "intrinsic ability to test" is lost when they reach school to a degree, they are encouraged to not push the boundaries of things and to conform to some form of normality. It's made me realise that I will try and help my children to never lose this ability, and not because I want them to grow up to be like their daddy, but to constantly push things and learn new things.

I believe we shouldn't lose this intrinsic ability, as it will help them in life both at school and at work in whatever they want to do, encouraging them to think outside the box when applicable, and to not always accept the first answer given to them... unless it's from Mummy or Daddy ;)

What does everyone else think?  Is this intrinsic ability "forced" out of children? Should children be encourage to grow or never lose this ability?



Labels:

Comments

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