Triaged Tester

January 9, 2009

Scenario testing – ways to create good scenario

Filed under: Black Box Testing,Tips — Triaged Tester @ 9:16 am
  1. Write life histories for objects in the system.
  2. List possible users, analyze their interests and objectives.
  3. Consider disfavored users: how do they want to abuse your system?
  4. List system events. How does the system handle them?
  5. List special events. What accommodations does the system make for these?
  6. List benefits and create end-to-end tasks to check them.
  7. Interview users about famous challenges and failures of the old system.   Study complaints about the predecessor to this system or its competitors.
  8. Work alongside users: see how they work & what they do.
  9. Read about what systems like this are supposed to do.
  10. Convert real-life data from competing or predecessor app.
  11. 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?

January 8, 2009

Designing Scenarios

Filed under: Black Box Testing,Tips — Triaged Tester @ 9:11 am

Scenario Designers rely on similar information to requirements analysis, but use it differently.

  • The requirements analyst tries to foster agreement about the system to be built. The tester exploits disagreements to predict problems with the system.
  • 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.
  • 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.
  • The tester doesn’t have to respect prior agreements. (Caution: testers who belabor the wrong issues lose credibility.)
  • The scenario tester’s work need not be exhaustive, just useful

Blog at