Wednesday November 13, 2019
What’s the difference between test cases and test scenarios? people often find it confusing in defining these two terminologies in software testing. To ease the burden, we have made an infographic representation out of the topic so that it will be easy to understand the test case and test scenario.
What is a test scenario?
A test scenario is a high-level use case or functionality to be tested. Each test scenario can be mapped to one or more detailed test cases. Test scenarios are derived by understanding the user expectation from the software and it is used by the user.
A good tester would cover all the test scenarios and functionalities. This document would then be used to derive the test cases. An example of a test scenario would be a login scenario that can consist of multiple test cases.
What is a test case?
A test case is a detailed step-by-step instruction to perform a series of actions or steps that help to validate a particular functionality in an application. A test case has the following main parts:
Difference between test case and test scnario
|Test case||Test Scenario|
|Detailed information about what to test, steps involved, expected result, etc.||Mostly contains one line information about what to test|
|Used for the validation of test output||It’s a thread of operation|
|Helps in agile testing||Helps greatly in exhaustive testing|
|Consumes a lot of time||Consumes less time compared to test case preparation|
|Serves as a proof guard for new testers||Helps in reducing complexity and repeatability of the product|
|Derived from test scenarios||Derived from use case|
|Can be used in future regression test cases||Used by new testers to save time|
How to write test cases?
Step 1: ID’ing the test case is very important. Each test case must have a unique ID for better traceability and accountability.
Step 2: Description of the feature or functionality that will be put to test must be added to each test case
Step 3: Conditions that have to be met before execution must be included
Step 4: Relevant data for the execution must be included in every test case
Step 5: The step required to execute the test must be included in detail
Step 6: Expected result before the execution along with actual result must be included