1. Introduction to Test Cases
A test case is a detailed set of conditions, steps, and expected results written to verify that a software application works as per the requirements. In manual testing, test cases act as a blueprint for testers. Even in 2026, with AI and automation growing rapidly, well-written manual test cases remain critical because:
They ensure consistency in testingThey help new testers understand the application
They are used as a base for automation scripts
They improve test coverage and quality
In companies like Amazon, Flipkart, TCS, Infosys, Accenture, Capgemini, Wipro, test cases are treated as official documentation and are often audited.
2. Why Writing Effective Test Cases is Important
Point-wise importance:
Ensures all requirements are tested
Reduces chances of missing critical defects
Helps in regression testing
Improves communication between QA, Dev, and Business teams
Saves time during re-testing and UAT
Acts as proof during audits and client reviews
3. Test Case vs Test Scenario
Test Scenario
High-level idea of what to test
Example: "Verify login functionality"
Test Case
Detailed step-by-step instructions
Example: Username, password, expected result, actual result
Real Company Example:
At Infosys, test scenarios are created first, and then multiple test cases are derived from one scenario.
4. Standard Test Case Template (Industry Level)
A professional test case usually contains:
Test Case IDTest Case Title
Module Name
Requirement ID
Preconditions
Test Steps
Test Data
Expected Result
Actual Result
Status (Pass/Fail)
Remarks
5. Diagram 1: Test Case Structure (Real Shape Diagram)
┌───────────────────────────────┐
│ TEST CASE │
├───────────────────────────────┤
│ Test Case ID │
│ Title │
│ Module │
│ Requirement ID │
│ Preconditions │
│ Test Steps │
│ Test Data │
│ Expected Result │
│ Actual Result │
│ Status │
│ Remarks │
└───────────────────────────────┘
6. How to Write a Test Case – Step by Step
Step 1: Understand the Requirement
Read BRD / SRS carefully
Clarify doubts with BA or Dev
Step 2: Identify Test Scenarios
Positive scenariosNegative scenarios
Boundary scenarios
Step 3: Write Detailed Steps
Each step must be clear
One action per step
Step 4: Define Expected Result Clearly
Avoid vague statements
Expected result must be measurable
Step 5: Review Test Cases
Peer review
Remove duplicates
7. Diagram 2: Test Case Writing Flow
┌──────────────┐
│ Requirement │
└──────┬───────┘
↓
┌──────────────┐
│ Test Scenario│
└──────┬───────┘
↓
┌──────────────┐
│ Test Case │
└──────┬───────┘
↓
┌──────────────┐
│ Review │
└──────────────┘
8. Example Test Case – Login Functionality
Test Case ID: TC_LOGIN_001
Title: Verify login with valid credentials
Precondition: User must be registered
Steps:
Open application
Enter valid username
Enter valid password
Click Login button
Expected Result:
User should be redirected to dashboard
9. Types of Test Cases
Valid input
Expected success
2. Negative Test Cases
Invalid input
Error handling validation
3. Boundary Value Test Cases
Edge conditions
4. UI Test Cases
Alignment, colors, fonts
5. Security Test Cases
Password masking
Session timeout
10. Diagram 3: Types of Test Cases
Test Cases
|
-------------------------
| | | | |
Positive Negative Boundary UI Security
11. Common Mistakes While Writing Test Cases
Writing vague steps
Missing expected results
Not covering negative scenarios
Duplicate test cases
Over-complicated steps
12. Best Practices for Writing Effective Test Cases
Use simple language
Keep steps reusable
Maintain proper naming convention
Link test cases to requirements
Update test cases regularly
Company Practice:
Capgemini & Accenture follow strict naming and version control for test cases.
13. Diagram 4: Test Case Life Cycle
┌───────────┐
│ Create │
└────┬──────┘
↓
┌───────────┐
│ Review │
└────┬──────┘
↓
┌───────────┐
│ Execute │
└────┬──────┘
↓
┌───────────┐
│ Update │
└───────────┘
14. Test Case Management Tools (Used by Companies)
Jira + Zephyr (Amazon, Flipkart)TestRail (Infosys, Wipro)
HP ALM (Banking Projects)
15. Diagram 5: Manual Testing Workflow with Test Cases
┌──────────────┐
│ Requirement │
└──────┬───────┘
↓
┌──────────────┐
│ Test Case │
└──────┬───────┘
↓
┌──────────────┐
│ Execution │
└──────┬───────┘
↓
┌──────────────┐
│ Defect │
└──────────────┘
16. Interview Questions & Answers (Test Cases – Manual Testing)
Answer: A test case is a documented set of conditions and steps used to verify whether a software feature works as expected.
Answer: Test Case ID, Title, Preconditions, Steps, Test Data, Expected Result, Actual Result, Status.
Answer: A test scenario is high-level, while a test case is detailed and step-by-step.
Answer: They validate system behavior for invalid inputs and ensure proper error handling.
Q6. Do companies still use manual test cases in 2026?
Q7. Can test cases be automated later?
Answer: Jira, TestRail, Zephyr, HP ALM.
17. Conclusion
Writing effective test cases is a core skill for every manual tester. No matter how advanced AI becomes, clear, structured, and logical test cases will always matter. Mastering this skill increases your value in interviews and real projects.