As with many terms, scenario means different things to different people in the world of software testing. In TETware we use test scenarios to tell the test case controller which test cases to process and how to process them. The scenarios are stored in a scenario file. The file may contain one or more scenarios, and they may be cross-referenced. The file is written is a simple, but powerful, scenario language.
Definition
Scenario testing is a software testing activity that 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 four key characteristics.
It is a story that is motivating, credible, complex, and 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.
Source:
http://www.onestoptesting.com/test-cases/scenario-testing/definition.asp
Definition
Scenario testing is a software testing activity that 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 four key characteristics.
It is a story that is motivating, credible, complex, and 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.
Source:
http://www.onestoptesting.com/test-cases/scenario-testing/definition.asp