Skip to main content

Movie Quotes applied to Software Engineering... "I've got a bad feeling about this" from Star Wars!

I finally got round to watching the new Star Wars (that's what it's like having 2 kids at home, babysitters are at a premium!!!), and (no spoilers here) but I was interested to see the following line being muttered again during the film! It reminded me of a series of blog posts I done a while back around famous movie quotes that have been said in films and applying them to Software Engineering/Testing... This particular quote has been said in every single Star Wars film so far! (Star Wars trivia for you there!) But for the purpose of this blog post, how does it apply to Software Engineering? 


Well, as Testers on a development team/project we get to see things that others perhaps don't get to see, we get to speak to everybody about the product that is being developed, we see it from a technical standpoint, from a business standpoint and from a customer standpoint, we really are in a truly unique position, and this is one of the things I love most about Testing.

As a result of this position, we can often find ourselves saying or thinking the above, which is great, providing you have evidence to back it up of course, nobody wants to work with a Debbie Downer!



If you have evidence to back up your particular feelings about a product, then it's perfectly fine to say something like the above, and hopefully people will listen to you and you can start to illustrate just why you have the bad feelings and how you can alleviate them and turn them into positive feelings!


Comments

  1. Game Over Man! Game Over! - Aliens

    ReplyDelete
  2. It will also allow you to maximize cost-effective production, as the software will assess the most efficient way to produce oil or gas. buy Revit Architecture 2015

    ReplyDelete
  3. In Motion3D Smash is an energizing logo uncover device for Movement 5, said Christina Austin, President of Pixel Film Studios. inMotion3D Smash obscures the line amongst expert and novice making this module a clear distinct advantage. FCPX Themes

    ReplyDelete
  4. My partner and I stumbled over here different website and thought I might as well check things out. I like what I see so now I’m following you. Look forward to checking out your web page repeatedly.

    selenium training in bangalore|

    ReplyDelete
  5. Yaahoo! Loved your post.You know i am also software tester and you said so true about testers position and also like star war series.I am big fan of your papersgear writing service review which are so commendable.Nice post.

    ReplyDelete
  6. Amazing work on the writer's part and This blog has a positive and excited outcome.
    holm law group san diego

    ReplyDelete
  7. Pleasantly astonished to see this meshwork of astounding words.
    here

    ReplyDelete
  8. Two free choices are overtly readily available, but not very as developer-welcoming: the open supply Iceberg as well as the free InstallEase, which was produced like a companion to the Absolute Deal with consumer management suite.

    FileWave's strategy has pros for license compliance and reclamation, along with flexibly deploying and redeploying purposes as required.

    Final Cut Pro 7 Torrent Mac - MacGIC

    ReplyDelete
  9. Every time I read this I get carried away by these words.
    https://123movieshub.it/

    ReplyDelete
  10. Watch here Deadpool 2 Movie Online Free you can watch latest movies onlione free here



    Watch Deadpool 2 Movie Online


    Deadpool 2 2018 Movie Online



    Watch Movies Online

    ReplyDelete
  11. Star Wars is an amazing movie. But I haven't observed this dialogue in all so far. I love these kind of movies. I'm also doing a degree program in Graphic Design.

    ReplyDelete

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...

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...

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...