Test scenario and Test case
Test Scenario
The requirement is divided into High Levels known as Scenarios We use test scenarios to tell the test case controller which test cases to process and how to process them. Test Scenario covers all the areas like Business logic, types of user profiles, etc.
Test Scenario Example
Verifying that a user can manage their Gmail inbox message, sent messages, logout, etc, with a valid user login and password.
Test Case
It is a document that describes an input, action, or event and its expected result to determine if an application’s functionality is working fine correctly.
Criteria for Writing Test Case
A fundamental criterion for writing test cases is to understand the requirement thoroughly. Once you understand the requirement is clear, you can start writing test cases.
Another criterion is your test case format should be ready.
Get Manisha Shukla’s stories in your inbox
Join Medium for free to get updates from this writer.
You should document all your requirements properly and make sure that for each and every requirement there must be at least one test case is covered.
Test Case Template:
- Test Case ID
- High-Level Description/Test Scenario
- Test Case Description
- Test Steps
- Expected result
- Actual result
- Status
- Defect ID
Testing Strategies in Software Engineering
It is a formal description of how a software product will be tested. It is developed for all levels of testing like — Functional Testing, Integration Testing, System Testing, Regression Testing, and also Automation if needed or not. The Testing team analyzes the requirement and writes Test Strategy.
RTM(Requirement Traceability Matrix) in Software Testing
It is also called the Traceability Matrix. A traceability matrix is nothing but a mapping between the requirement and Test Cases RTM is a document associated/linked, or mapping between requirement and Test Cases. This helps in how many test cases are written for a particular requirement. All Test Cases for the specified requirement are captured or not.
- Are we testing all the requirements?
- How many Test Cases are there for particular modules, are we covering all?
