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

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