Skip to main content

Famous Movie Quotes applied to Software Engineering - Cool Hand Luke

I thought it might be a bit fun to do a series of blog posts where we take a famous movie quote, and apply it somehow to QA/Testing or even the software engineering life-cycle.

This is one famous movie quote, and I think it applies greatly to Engineering in general (or anywhere in fact)! I don't think a week has gone by in my career where I couldn't have uttered the following:

What we have here is a failure to communicate (Cool Hand Luke)

I saw this quote (although I haven't seen the film), and I don't even think it needs any explanation....

But I'll explain anyways! I would say that 80% of problems that are in a workplace are down to a failure in communication, if a bug is found, a failure to communicate the effects of the bug properly can lead to a false severity, or a false priority. That's not the only time when a failure to communicate can be damaging, especially for QA, but a failure to communicate when understanding requirements or when explaining what you are testing can lead to a misunderstanding and unnecessary confusion.

Stay tuned for more quotes from top films such as Top Gun, Casablanca, Forrest Gump and more!
Labels:

Comments

  1. www.IHateIreland.com21 August 2013 at 03:53

    "I'll be back".
    That infamous bug that keeps on returning because the regressions tests don't cover it.

    ReplyDelete
    Replies
    1. Gareth Waterhouse21 August 2013 at 04:59

      Ha, that's a good one! I hadn't thought of that one... I had thought of one from the same film though, but I'll share that at a later date!

      Delete
  2. Unknown22 August 2013 at 12:06

    What would you link to 'I think we're going to need a bigger boat'?

    ReplyDelete
    Replies
    1. Gareth Waterhouse23 August 2013 at 01:12

      http://www.testingthewaterhouse.com/2013/08/youre-gonna-need-bigger-boat-jaws.html

      You read my mind!

      Delete
  3. Mangosteen for a Better life.30 December 2013 at 17:02

    That quote is wrong. What he said was "what we have here is 'failure to communicate' "

    ReplyDelete
  4. Unknown16 January 2018 at 14:01

    Pleasantly surprised to see this meshwork of amazing words.
    resumeyard.com

    ReplyDelete
  5. BigTechiess18 January 2018 at 11:15

    too much amazed to see the work
    cracksmalta

    ReplyDelete
  6. Zdeněk Šrámek7 June 2018 at 11:50

    Wow, thank you for such a nice post!

    CLIP STUDIO PAINT EX 1.7.4 Crack

    ReplyDelete
  7. Miriam Trevor16 October 2018 at 10:38

    great.
    http://www.testingthewaterhouse.com/2013/08/famous-movie-quotes-applied-to-software.html

    ReplyDelete
  8. sandeep saxena9 March 2019 at 01:59

    Thanks for publishing this blog, really awesome. Only experienced professional can do this.
    QTP Training in Chennai
    QTP Course in Chennai
    Best QTP Training Institutes in Chennai
    QTP Training in Porur
    QTP Training in T Nagar
    LoadRunner Training in Chennai
    Best Loadrunner training institute in chennai
    performance testing training in chennai

    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