Tutorial 8: To design test cases.
This document is for your understanding. after reading this you have to make 2 test cases.
To design test cases, you need to systematically create scenarios that check whether a
software application works as expected.
Here’s a step-by-step guide 👇
🧩 1. Understand the Requirements
Study the SRS (Software Requirement Specification) or user stories.
Identify functional and non-functional requirements.
Clarify any doubts before you start designing.
🧠 2. Identify Test Scenarios
A test scenario is a high-level idea of what to test.
Example: “Verify login functionality with valid and invalid credentials.”
🧪 3. Design Test Cases
Each test case is a detailed instruction on how to test a specific function.
Test Case Template:
Field Description
Test Case ID Unique identifier (e.g., TC001)
Test Scenario What functionality is being tested
Pre-Conditions What needs to be true before the test
Test Steps Step-by-step instructions
Test Data Input values
Expected Result What should happen
Actual Result What actually happens (filled during execution)
Status Pass/Fail
Priority/Severity Importance of the test
🧮 4. Apply Test Design Techniques
Use systematic techniques to find effective test cases:
Equivalence Partitioning (EP): Divide input data into valid and invalid classes.
Boundary Value Analysis (BVA): Test at the edges of input ranges.
Decision Table Testing: For combinations of conditions.
State Transition Testing: For systems that depend on previous states.
Error Guessing: Based on experience of where bugs usually occur.
🧰 5. Review and Traceability
Review test cases for completeness and clarity.
Maintain Traceability Matrix to map requirements → test cases.
(Ensures every requirement is tested.)
✅ 6. Example Test Case
Field Example
Test Case ID TC001
Scenario Verify login with valid credentials
Precondition User must be registered
1. Open login page
Steps 2. Enter valid username & password
3. Click “Login”
Test Data Username: john123, Password: abc@123
Expected Result User is redirected to the dashboard
Actual Result To be filled after execution
Status Pass/Fail