Skip to main content

A Bug's Life? Brought to you by QA Films

My 3 year old son has been watching A Bug's Life recently, and he seems fascinated by it, and rightly so, it's an awesome film.

For those that haven't seen A Bug's Life, it's about an ant called Flik who goes away to try and save his colony from evil invaders (Grasshoppers), I won't spoil it for you by revealing the outcome of the film, but it's a thoroughly enjoyable film!

It got me thinking this morning, about a different type of bug, the bug that we're all aware of, one that is a bug in software...

How can this film relate to testing?

Well, I like to think of myself (and other Testers) as Flik, someone who is trying to prevent bugs (Grasshoppers) from spoiling software (Flik's colony), whilst I don't find a circus, I do have a team of testers who I trust to help prevent the bugs from making it to live, and to help improve processes for the future to help prevent bugs before they're even coded.

What other films can you think of that could be applied to software testing?  What about Independence Day and fighting off the aliens (bugs)... Although I would liken that to a project that looks doomed that brings in a team to help firefight the bugs.


  1. Pleasant post. I was checking always this site and I am inspired! To a great degree supportive data uniquely the last part I nurture such information a ton. I was looking for this specific data for quite a while. Much obliged to you and good fortunes. agile software testing

  2. Immensely dumbfounded by the words utilized by the author.
    holm law group san diego

  3. When you understand and realize all the intricacies that go into creating an audio-visual presentation or a movie, you can see whether what you are being presented with was done with care and with you in mind or without any thoughts and doesn't really deserve your attention.

  4. The down to earth approach of the essayist in this blog is commendable.


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…