Q: What is the typical role of a Software Tester? Simple answer: Find all the bugs before release! In reality, it depends on the maturity of the organization and the processes they have in place. A good tester should be able to identify the proper test cases from the available information, document the tests in some way, execute them and analyze the results. If the test results in a defect being discovered, the Software Tester then needs to report it in a manner that leads to it being resolved. The Software Tester is the stakeholders' advocate - they should always focus on what provides value to the stakeholders (including the end-user). Q: What are some of the challenges Software Testers face in the workplace? One of the biggest is the lack of understanding of what should be the role of the Software Tester . Most of the other problems stem from decisions made without this proper understanding. So, testers are often brought onto a project late, with little or no time to prepare. The budget often doesn't provide for adequate test resources and tools to do the job. Finally, testers are rarely given all the information they need to do an effective job. Sometimes it's even difficult to find out who has the information. All of the above is usually worse for automated testing. Q: What are the qualities of a Software Tester? I recently read a blog post comparing Software Testers to forensic investigators - we're the CSI of software development! I like this analogy, because it highlights that a tester should be skilled and inquisitive. Skilled: I am constantly studying all aspects of software systems in general and development and testing in particular. I need to know how things work if I'm going to find the places they're likely to fail. Inquisitive: The tester needs to explore each bug to 1) boil it down to the simplest case that reveals it and 2) expand the parameters to see if it's part of a larger collection of faults. Q: If you were to hire a Software Tester which questions would you ask? I've been finding more testers can only give text book answers to questions. They don't know how to apply it to real-world situations. I'm going to ask about problems they faced at prior jobs, how they solved them, were they successful or not, and what they learned from it. Then I'll ask questions based on the position they'd be coming into. It's not about right/wrong answers as much as about thinking, analyzing and solving. (I might focus more on the right/wrong answers for junior testers, but I still want to see how they think. Teaching how to test takes less time.) About Philip: I've been in IT for a dozen years, starting in Technical Support. Domain knowledge (from prior jobs) and technical skills opened an opportunity for me to move into testing and I knew I found what I wanted to do. Primarily, I've done test automation, but I've also done my share of manual testing, as well as Quality Assurance/Process Improvement. I've been fortunate to lead a team of testers and to act as a mentor to junior testers. I have a Bachelor's Degree in Mathematics from the University of Miami. I'm also a sometime musician, actor and stunt man. (No, really!) |