QA - Cheatsheet
Test plan vs test suite vs test case
Side-by-Side Comparison
| Feature | Test Plan | Test Suite | Test Case |
|---|---|---|---|
| Focus | Strategy & Scope ("The Big Picture") | Organization & Category ("Logical Grouping") | Execution Steps ("Granular Validation") |
| Level | High-level artifact. | Mid-level container. | Low-level detailed document. |
| Answers | What, why, who, and when to test. | Which tests belong together. | How to test a precise action. |
| Created By | QA Managers or Test Leads. | QA Leads or Senior Testers. | QA Engineers and Testers. |
| Modifiability | Infrequent updates (per milestone or sprint). | Medium updates (as features evolve). | Highly dynamic (updated with code fixes). |
- Test Plan: Scope, schedules, resources, hardware/software requirements, risk management, and pass/fail criteria.
- e.g. "We will test the new checkout system for the e-commerce app over the next two weeks using 3 manual testers and 1 automation engineer on Chrome and iOS platforms.".
- Test Suite: A collection of test cases that are logically grouped together based on functionality, feature, or testing type.
- e.g. Common groupings include Regression suites, Smoke testing suites, Security suites, or feature-specific groups (e.g., "Login Functionality").
- Test Case: A detailed document that specifies the exact steps, inputs, expected results, and execution conditions for testing a specific functionality or feature. It provides granular validation to ensure that the application behaves as expected under defined conditions.
Real-World Analogy
Think of organizing a major music festival:
- The Test Plan is the festival organizer's operations guide (budgets, dates, security plans, and vendor locations).
- The Test Suite is the schedule for a specific stage (e.g., the "Rock Stage" lineup vs the "Electronic Stage" lineup).
- The Test Case is the exact setlist and audio settings required for one specific artist's 45-minute performance.