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

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

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more