Monday, September 8, 2008

Who Tests the Tester?

Finding the right tester to join your team  is tricky business. For one, software testing is not something many people have degrees in. Instead it is something most people learn on the job, which is a bit of a chicken and egg situation in of itself. Secondly, it seems many people only visit the testing profession rather than making a career of it, so the people with the right experience might not be interested in the job.

One thing we do we selecting candidates for an open Test Engineer position is to go give a quiz. In its current form it is only six questions that we give people up to an hour to answer. This provides a good level-set for what kind of tester a person is likely to be.  I won't share the exact questions here in case some savvy applicant finds this blog. I will however give this much info:
  • Some of the questions are about what test cases would you write to test some made up app
  • Some of the questions deal with when it is best to use different styles of testing
  • One of the questions is a trick question - it asks about how you can tell when you've found all the bugs in an app. No one has gotten this one right yet.
The reason I am thinking about this now is because we are trying to find the right tester to fill a new position at my company, AdaptiveBlue. If you might be the one, or know someone who might be, please let me know.

5 comments:

Philk said...

There have been quite a few discussions recently about the lack of quality testers, have you been struggling to fill the hole ?

Good luck in finding a good candidate and maybe an idea for a follow-up blog will be to tell us how easy/hard it was to find the right candidate

Mark said...

Presumably the correct answer to the last one is never - you can't possibly KNOW that you've found all the bugs, and even if you mathematically proved them to be functioning correctly, the behaviour can change and the specifications required of the software and indeed the tests can change, rendering your tests incorrect.

MacroTesting said...

Very Good article, i really like it. I am doing a bit on research about Software Testing and i found also macrotesting www.macrotesting.com to be very good source.

Thanks for your article

Regards,
Prem

hackdon said...

If, according to TDD, you should write unit tests before you write the tests. Shouldn't you write tests for the tests, since the unit tests themselves are code?wer

QualityPoint said...

Nice Tricks to test the testers!!!
Software Testing Quiz Questions