What is a Test Scenario?

Test Scenario – Test Scenario includes all functions that can be tested. Test Scenario is also called Test Condition or Test Possibility. As a tester, you can put yourself in the shoes of the end user and find out the real-world and possible scenarios of the application under test.

Scenario Testing is a variant of Software Testing in which Scenario is used for testing. Scripts make it easy to test complex systems.

Why create Test Scenario

Test Scenario is useful when a tester cannot do a comprehensive software test due to time constraints. Test scripts allow them to test the software’s functionality on the most important aspects in relatively less time. And so Test Scenario was created for the following reasons:

• Create test scripts that ensure Test Coverage is complete
• Test scenarios can be adopted by various stakeholders such as Business Analyst (BA), Developers, Client to ensure the application is tested thoroughly and ensure that the software is working properly. .
• Test scenario as a quick tool to define testing efforts, thereby creating recommendations for customers or organizations about workforce.
• Test scenarios help to identify the most important end-to-end transactions or determine real-world use of software applications.
• To study terminal functionality, Test Scenario is very important.

However, for some projects we cannot create Test Scenario:

• The application under test is complex, unstable, or the project is falling into a time of crisis.
• Agile Method-driven projects such as Scrum, Kanban may not generate Test Scenarios.
• Test scripts may not be created when correcting new errors or when performing a regression test. In such cases, the Test Scenario must be much saved in previous test cycles. This is especially true of maintenance projects.

What is the difference between Test Scenario and Test Case?

Test Case continues to go into more detail on test scenario details. Test Cases are like the smallest units of each test project, like the cells of a living organism.

Concept

• Test Cases: Provides detailed information on what to test, steps taken and expected results. Test Scenarios again provide a stream of information about what to check.

Advantages and disadvantages of each

1. Advantages and benefits

Test Cases:

• Can be reused many times in the future.
• In terms of time, test case creation is very useful in bug reporting. The tester only needs to provide the reference of the test case ID without mentioning the details.
• This document will be really important for new graduate testers who do not have experience in system testing

Test Scenarios:

Save time and actively generate new ideas, it’s favored by the new generation of the software testing community.

• Modifications and additions are simpler and are not assigned to a specific person.
• For a large project where a group only knows specific modules, using Test Scenario provides an opportunity for people to easily discuss and come up with ideas while looking at other modules. .
• Test Scenario can achieve the best coverage by splitting applications on the other hand it also reduces product repeatability.

2. Disadvantages:

Test Cases:

• It takes time and money because it requires a lot of human resources to be able to understand the details of what to test and how it can be tested.

Test Scenarios:

• If Test Scenario is created by a particular person then users will not be able to fully understand the previous person’s idea, it will need more group discussions so it will take a lot of effort to clarify previous scenarios.

So use Test Case or Test Scenario

Test Cases are like the smallest units of each test project, like the cells of a living organism. The important thing when setting up a test case:

• At least possible step and make sure only 1 verify step needs to be performed.
• Expected result must be explicitly described. An example for ambiguous description is as follows: “test pass when user login is successful”. How successful? What proves login successful? Which screen will the app or web redirect the user to? What determines that the user has been logged in? All must be stated as clear as possible. This is paramount if you want the test case to be automate.
• Pre-condition must be clearly described. What features must be active before the test case can run? Testers must do before starting test cases? Which test cases need to pass before we can run the current test case?

Meanwhile Test Scenario goes deeper into the details of each feature. Test Scenario describes what to test, note what to test. Here can be an example of a typical test scenario such as: Test Login function

• Check whether the text content on the login page is correct according to the design or not
• Check the Username field
• Check the Password field
• Check that the Login button is working properly as designed or not

When the project does not have much time, Test Scenario will be an optimal choice for the project. And it is still as effective as creating Test Case.

How to create a Test Script

As a Tester, you can follow these five steps to create Test Scenario:

• Step 1: Read the required documents such as BRS, SRS, FRS of the System under Test (SUT). You can also refer to the uses cases, books, instructions … of the application to be tested.
• Step 2: For each request, figure out the possible user actions and goals. Identification of technical requirements aspects. Identify possible situations of system abuse and judge the user with the hacker in mind.
• Step 3: After reading the Requirements Document and performing Analysis, list the test scenarios to verify each feature of the software.
• Step 4: Once all possible test scenarios are listed, the Traceability Matrix is ​​created to verify that every requirement has the corresponding test scenario.
• Step 5: The generated scripts are reviewed by the supervisor and stakeholders in the project.

Example of a Test Scenario for a banking website Test scenario 1: Test loggin functionality and authentication of loggin screen Test scenario 2: Test of remittance functionality can be done correctly in the field the balance of the user whose balance is less than the amount transferred. Test scenario 3: Test of remittance functionality can be performed properly in case the user balance has a balance equal to the transferred amount Test scenario 4: Test of remittance functionality can be done correct in case the user balance has a balance greater than the transfer amount Test scenario 5: Testing whether account statement functionality is viewable Test scenario 6: Test of deposit function Recurring / recurring deposits can be created

Note:

• Each test scenario must be associated with at least one requirement in the project.
• Before creating a test scenario that verifies multiple requests at once, make sure there is a test script for each individual request.
• Avoid creating test scripts that are too complicated with many requirements.
• The number of scenarios can be large and costly to cover them all. Based on customer preferences, run only the selected test scripts.