Triaged Tester

March 18, 2009

Stop Testing

Filed under: Black Box Testing,General,Test Management — Triaged Tester @ 9:14 am
Tags: , , ,

Time and again the most important question that haunts a tester – when are you stopping your test?

Well’ there is no right or wrong answer for this. But definetly you can concur at the time to stop testing using these items

1. All high priority bugs are fixed

2.The bug convergence shows good result

3. ZBB ( Zero Bug Bounce) has been achieved

4.The testing budget is achieved

5.The project duration is completed 🙂

6. The risk in the project is under acceptable limit

Practically item # 6 would be the main and most acceptable solution to stop testing.  Now what risks need to be monitored for these answers ? . I would go with – Test coverage, Number of test cycles & priority of open  bugs


January 7, 2009

Scenario Testing

Filed under: Black Box Testing — Triaged Tester @ 9:01 am

A scenario test is a test based on a scenario. A scenario typically involves a sequence of steps or tasks. The tests are based on a story about how the program is used, including information about the motivations of the people involved. Usually the story involves a complex use of the program or a complex environment or a complex set of data. The story needs to be realistic. It not only could happen in the real world but also make the stakeholders believe that something like it will probably happen. The story needs to be motivating, only then will a stakeholder with influence would push to fix a program that failed this test.

Why Scenario Test?

  • Expose failures to deliver desired benefits.
  • Connect testing to documented requirements.
  • Bring requirements-related issues to the surface, which might involve reopening old requirements discussions (with new data) or surfacing not-yet-identified requirements.
  • Detect errors in the interaction of two or more features.

Create a free website or blog at