Tester Mentality

I tech screened a tester this morning for a position on my team. I always ask the candidate to describe the tester mentality. I loved today's interviewee's answer:

More than the product working perfectly without any crash assert, if it is not intuitive and user friendly it is useless. What will the customer use it for? Does it provide value for the scenarios the customer cares about? Think of the variety of customers - not everybody will have a top-of-the-line machine, or the same technical expertise, or the same expectation of the product. More than just breaking software, the tester should make sure it has the capabilities the customer needs.

Right on! This is what our automation stack is all about - keeping that customer focus.

If you aren't thinking about your customer, keeping them in mind as you test, then you aren't testng.

Comments (2)

  1. Yeah – since the tester is the first customer for the product, it becomes imperative that we check the prod for usefulness from the customer view point. Many times, I’ve noticed that it is at the spec level itself that most of these jarring things can be trapped. The feature just doesn’t seem right at inception itself whereas sometimes it takes the dev to actually put the feature in front of you to realise that! I guess a good tester must be able to detect these as early on in the product as possible.

    And as a tester testing a testing tool(VSTT), you bet I feel *closest* to the customer 🙂

Skip to main content