[Me]:- Guruji, How do we design scenarios for testing?
[Guruji]:- Scenario Designers rely on similar information to requirements analysis, but use it differently.
[Me]:- oh, so how does a requirement analyst differ from Tester in this aspect.
[Guruji]:- That's a good question.
| Requirement Analyst | Tester |
| The requirements analyst tries to foster agreement about the system to be built | The tester exploits disagreements to predict problems with the system |
| Has to make conclusions and recommendations as to how the product should work | The tester doesn't have to reach conclusions or make recommendations about how the product should work. Her task is to expose credible concerns to the stakeholders |
| Can make product design tradeoff's by exposing consequences | The tester doesn't have to make the product design tradeoffs. She exposes the consequences of those tradeoffs, especially unanticipated or more serious consequences than expected |
| Has to respect prior agreements with stake holders | The tester doesn't have to respect prior agreements. (Caution: testers who belabor the wrong issues lose credibility.) |
| Work is exhaustive | The scenario tester's work need not be exhaustive, just useful |
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
Get Free Email Updates to your Inbox!
