Skip to main content

Movie Quotes applied to Software Engineering... Nanny McPhee


The above quote as you can see is from Nanny McPhee, and it's as follows:

"When you need me but do not want me, then I must stay. When you want me, but no longer need me, then I have to go"

I think this applied very much to my role as a QA Lead, I seem to spend time with teams who need me, more than teams who don't. This isn't a bad thing, I know teams that don't need me will do fine without me, and by helping other teams I help improve them and improve their processes. I recently read a blog by James Bach here and I think this relates to the above, in that I jump (as James says, A Test Jumper) into help teams as and when I can and as and when it's needed, if teams don't necessarily need my help then I will spend less time with them. Every team is different and has different needs and different level of needs.

I've also said the above to an Agile Coach we had who blogs here, I often said to her that she's only around whilst we need her, and unfortunately once we didn't need her, she had to go, no matter how much we wanted her to stay.

Does this apply to your role? Or are you on the receiving end of this? Either way, feel free to comment, or comment if you don't agree! :)


Labels:

Comments

  1. Muhammad Hassan10 March 2018 at 09:22

    Excellent and very exciting site. Love to watch. Keep Rocking. Teknik Menggunakan File Lock PC - Avoid Hang Around Looking, Read through Concerning Cellular Desktop computers Within this article password protect folders xp

    ReplyDelete
  2. Muhammad Hassan18 March 2018 at 08:48

    Cant Play Videos In A Folder Lock On An PC - Don't Waste Time Looking, Study About Cellular Desktops Right here aharon

    ReplyDelete
  3. Kevin Dellinger23 January 2019 at 03:12

    Thank you, I've just been searching for info about this subject for ages and yours is the greatest I've discovered till now. But, what concerning the conclusion? Are you certain concerning the supply? Click here for info: The Ultimate Guide To Encryption Software & You Knew How To How To Encrypt A Password For Free But You Forgot. Here Is A Reminder

    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