Issuu on Google+

QATestLab 154a, Borschagivska str., Kiev, Ukraine ph.: +38(044)501-55-38

What Is Scenario-Based Testing and When Should We Use It? Part I Scenario-based testing is one method of documenting software specifications and requirements for the project. Scenario-based testing is used for writing tests for individual user scenario, which would check their work. Scenarios concentrate on the principal objectives and requirements. If the scenario runs from start to finish, then it passes.

Scenario-based software testing can be shown as inspection-based collection of tests, which are performed to verify that the user can perform the desired actions completely from beginning to end. There are other ways to show scenarios, such as a table, where the first column is intended to describe the actions of the user, and the second is used for the response of the system. To avoid duplication of the same scenarios, the second part can be provided as a set of alternative inputs, particularly if it is connected with a large amount of components and parts of the system. In fact, it is a test designed to make sure that all parts are combined in an expected way. Finally, however, all projects need to check that these user scenarios are performed correctly, as most problems arise not because of the individual components, but because of their connections and interactions.

(c) QATestLab, 2012

What Is Scenario-Based Testing and When Should We Use It? Part I