Scenario testing - ways to create good scenario

[Me]:-  I tried writing some scenarios for testing. But i was lost midway. can you guide me ways to create good scenarios

[Guruji]:- Well , while you create scenarios, bear in mind the blow pointers. It will tremendously help you.

List possible users, analyze their interests and objectives

Consider disfavored users: how do they want to abuse your system?

List system events. How does the system handle them?

List special events. What accommodations does the system make for these?

List benefits and create end-to-end tasks to check them.

Interview users about famous challenges and failures of the old system.   Study complaints about the predecessor to this system or its competitors.

Work alongside users: see how they work & what they do

Read about what systems like this are supposed to do.

Convert real-life data from competing or predecessor app

Look at the specific transactions that people try to complete. What are all the steps, data items, outputs, displays, etc.?Look for sequences: typically do task X in an order. What are the most common orders (sequences) of subtasks in achieving X?

Read more

Designing Scenarios

[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

 

Read more