Tester as a business analyst

Posted by P R Karve | Aug 23, 2010 |

Many development teams tend to underrate a tester, especially a manual tester, assuming that anybody can do what he does. As a result, he doesn't get the importance and respect he deserves. Project managers and developers normally interact with the business analysts and / or customers. The outcome of these interactions is then documented as the requirements.

Actually, to be able to do justice to his role the tester needs to really have a good grasp of the business domain the software is part of. The requirement specifications may be sufficient to test the happy paths. But to come up with the right tests for different possible scenarios, he must thoroughly understand the domain. The tester would do well to acquire business analysis skills. It will give him an edge and help to create a robust product. It will give him direct exposure and place him at his rightful place in the requirements chain.

0 Comment for this post

Post a Comment

Required Information *

In accordance with our comment policy, we encourage comments that are on topic, relevant and to-the-point. Once submitted, your comments will be published by the Impetus blog moderator. We will remove comments that include profanity, personal attacks, racial slurs, or threats of violence, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.