Print Page | Close Window

Scenario Testing

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Plans @ OneStopTesting
Forum Discription: Discuss, Learn and Prepare better and better Test Plans for yourself.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=522
Printed Date: 24Dec2024 at 2:14pm


Topic: Scenario Testing
Posted By: varsha
Subject: Scenario Testing
Date Posted: 02Apr2007 at 11:46pm
What is Scenario Testing?

Def#1:
Scenario testing is used to create large test cases that model real use of the application by covering multiple requirements. These tests are used to find bugs in the system, learn the product, and find requirements problems. Scenarios should be real life examples of system use, but exaggerated to test extreme use, like a soap-opera. However, scenario testing does not provide code coverage, and it is a black-box testing approach that should be used later in development.

Transaction flow testing looks at the different processes and decision points in a transaction of the system. This is a way to model a scenario and test all of the branches in a particular transaction.


Def#2:
Scenario testing is a software testing activity. It uses scenario tests, or simply scenarios, which are based on a hypothetical story to help a person think through a complex problem or system. They can be as simple as a diagram for a testing environment or they could be a description written in prose. The ideal scenario has five key characteristics. It is (a) a story that is (b) motivating, (c) credible, (d) complex, and (e) easy to evaluate. These tests are usually different from test cases in that test cases are single steps and scenarios cover a number of steps. Test suites and scenarios can be used in concert for complete system testing.



Print Page | Close Window