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

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more