Scenario testing involves using real-world scenarios rather than test cases to test software. Testers think like end users to determine scenarios that could be performed in the software. Scenarios are created with input from clients, stakeholders, and developers. Scenario testing verifies full functionality and ensures business processes and flows match requirements. It also tests common use cases. System scenario tests focus on realistic user activities covering system components, while use case scenarios provide step-by-step procedures for intended user roles interacting with the system.

1. SCENARIO TESTING

2. WHAT IS SCENARIO TESTING?
▧ Scenario Testing in software testing is a method in which actual
scenarios are used for testing the software application instead of test
cases.
▧ In scenario testing the testers put themselves in the end users shoes
and figure out the the real world scenarios or use cases which can be
performed on the software by the end user.
▧ In scenario testing, testers take assistance from clients, stakeholders
and developers to create test scenarios.
2

3. 3

4. Why do we write test scenario?
▧ The main reason to write a test scenario is to verify the
complete functionality of the software application.
▧ It also helps you to ensure that the business processes and
flows are as per the functional requirements.
▧ It ensures that the software is working for the most common
use cases.
4

5. Strategies To create good scenarios :
▧ Enumerate possible users their actions and objectives.
▧ Evaluate users with hacker's mindset and list possible
scenarios of system abuse.
▧ List the system events and how does the system handle such
requests.
▧ Read about similar systems and their behaviour.
▧ Studying complaints about competitor's products .
5

6. 6

7. Example of test scenario:
For an eCommerce Application, a few
test scenarios would be,
○ Test Scenario 1: Check the Search Functionality
○ Test Scenario 2: Check the Payments
Functionality
○ Test Scenario 3: Check the Login Functionality
7

8. 8

9. 9

10. 10
SCENARIO TESTING
SYSTEM SCENARIO USE CASE SCENARIO

11. SYSTEM SCENARIO
Scenario tests used in this method are only those
sets of realistic, user activities that cover various
components in the system.
11

12. APPROACHES TO DEVELOP SYSTEM SCENARIO
▧ Story lines
▧ State transitions
▧ Business verticals
12

13. STORY LINE
▧ Develop a story line that combines various
activities of the product that may be executed by an
end user.
13

14. STATE TRANSITIONS
▧ Consider an object ,derive the different
transitions/modifications that happen to the object,
and derive scenario to cover them.
14

15. BUSINESS VERTICALS
Business Vertical Testing is testing such products
for different business domains.
For example ,
 Banking
 IT industry
 Medical
 Manufacturing
15

16. USE CASE SCENARIO
▧ A use case scenario is a stepwise procedure on how a user
intends to use a system with different user roles.
▧ A use case scenario can include stories, pictures, and
deployment details.
▧ Use cases are useful for explaining customer problems and
how the software can solve the problems without any
ambiguity.
16

17. ▧ Users with different roles == Actors
▧ Product should do for a particular activity ==
System behavior
▧ Users to interact with the actors and system ==
Agents
17

18. 18

19. 19

20. 20