Skip to main content

Not sure about something? Ask questions...

Recently I was watching Zoolander (it's an amazing film, and one I can highly recommend), and Derek Zoolander (Ben Stiller) plays a dumb male model in it, but it's hilarious. One scene however got me thinking, and it's this scene here:



"Did you think I'd be too stupid to know what a eugoogly is?"

It shows Derek not knowing something and being too afraid to ask for fear of looking stupid. It's something that unfortunately I still see, and one of the reasons why I believe that Testers need to understand what they are testing, but all too often, I see Testers scared to ask questions.

If a Tester is scared to ask questions, then that raises alarm bells on multiple fronts:

- Firstly, is the team a safe environment for the Tester to ask any questions? Do they feel confident and comfortable in front of their fellow team mates.
- Secondly, if the Tester doesn't truly understand something, then how do they know how to test it? What test cases to write and execute?
- Finally, if they are scared to ask questions then they need to work on their self confidence, it's far better to ask a question early on, remember, feedback early is critical in all aspects of life!

So, how can a Tester overcome the above or at least attempt to?

The answer in short, is that it's very difficult for a Tester alone to conquer the above, it's a team mindset. Having said that, there are things a Tester can do to help the team appreciate and become engaged in the process.

For the first point, if the team isn't a safe environment, if they don't feel comfortable then how can they tackle that? How can you improve the relationship between members of the team? This is a difficult question as it can be quite team specific, maybe it could be that the team need to work closer together and appreciate the work that others do? Pair and then pair some more, not just paired programming, but paired testing too! Or it may be that they need to just do some good old fashioned team bonding! We often have team away days here, and they're a great way to get to know others in the team and people always come back feeling closer and more of a team after a successful away day!

Sometimes I think it's easy to get bogged down with work and you forget that everyone in the team is a person too, they all have a life just as complex if not more complex as yours, so ask them questions about their day, what they did last night, that sort of stuff. I've mentioned in the past that by divulging some personal information about yourself people feel like they know you and are more likely to open up.

For the second point, if a tester doesn't understand something then research it, whether that's Google, Bing, YouTube, Pluralsight... There is an infinite amount of resources at our fingertips, we need to take advantage of the situation we find ourselves in with the Information Highway! Failing that just ask a developer that you are comfortable talking to if you're not sure.

Finally, and the solution to the last point is fairly obvious, just ask questions, swallow your pride and ask a question if you're not sure. The earlier you ask a question the better, just like in testing the earlier you give feedback the better! This is why it's essential to get Testers involved early, not just because they may ask about requirements etc. and question them, but it helps them to understand the technology and what is being developed, otherwise they will always be playing catch up with the developers in the team.

The 3 key things to take away from this article are:

1 - Do not be afraid to ask questions - If you do not understand something, ask a question...nobody will think it's a stupid question.
2 - Work closer with the team, it's about how WE test it, how WE deliver quality - By working closer you get to know information without necessary asking questions and this works both ways
3 - Ask early and often - The earlier you ask a question the better, as the more value that it will bring for you and the team

Comments

  1. Great Blog! If you are not sure or confident about anything than ask questions and clear your doubts about that particular matter.

    ReplyDelete
  2. What i do not realize is actually how you're not actually much more well-liked than you might be now. You're very intelligent. You realize thus significantly relating to this subject, made me personally consider it from a lot of varied angles. Its like women and men aren't fascinated unless it’s one thing to accomplish with Lady gaga! Your own stuffs outstanding. Always maintain it up! website design agency singapore

    ReplyDelete
  3. I discovered your blog site on google and test a number of of your early posts. Continue to maintain up the very good operate. I simply extra up your RSS feed to my MSN Information Reader. In search of ahead to studying more from you in a while!…怎么写简历

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

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

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