Scenario-Based Testing: when should we use It?
20 June 2012
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.
Scenario-based testing is best suited for the following cases:
- In some applications, for example applications that are used by certain users in the company or internal technological applications, this lead-up may be sufficient. Random people don’t have access to such applications, so the number of casual intruders can’t be large.
- This approach is also well used for usability tests. If a specialist in usability testing has a scenario, that he can accompany the users through the interface and provide them with a set of interactivities. The goal of this approach is to prove poor designs or user expectations that may not have been implemented.
- If the engineering department is concentrated on the persecution of the last software bugs in the program code and detailed unit testing, the testing team can only combine the elements together and make sure that the interaction interfaces work correctly. Nevertheless, this approach does not give an absolute guarantee that many of the mistakes and security breaches are not present in the project, despite the fact that the simple inspections did not reveal them.
- Scenario-based testing is suitable in the best way for end-to-end testing. The presence of the full scenario provides complete user interaction with software and ensures that the elements of engineering process are not visible to the user.