[Me]:- Guruji, I have been hearing a lot of things about Scenario Testing. Can you tell me what it is?
[Guruji]:- Sure , 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.
[Me]:- But why Scenario test?
[Guruji]:- Well, you can use Scenario tests to
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
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
