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.






Comments

  1. historypak4 September 2017 at 07:48

    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

    ReplyDelete
  2. Bk_Service30 December 2017 at 06:53

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

    ReplyDelete
  3. James harper11 January 2018 at 05:23

    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. 123movies.one

    ReplyDelete
  4. Star19 May 2018 at 14:07

    The down to earth approach of the essayist in this blog is commendable.
    https://123movieshub.it/

    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