Test case vs test scenario
Updated 2026-11-13 · 2 min read
Turn a broad test scenario into executable cases with data, preconditions and observable expected results. Includes a comparison table, concrete examples and an interview answer.
The difference in one table
| Aspect | Test case | Test scenario |
|---|---|---|
| Detail | Specific conditions, inputs and expected results | A behaviour, journey or condition to examine |
| Purpose | Make a particular check repeatable | Identify coverage areas and user risks |
| Example | Expired coupon is rejected without changing total | Apply a coupon during checkout |
| Relationship | One of several checks under a scenario | Can lead to several positive and negative cases |
| Format | Written steps or executable test logic | Often a short statement or flow |
Examples
Scenario: apply a coupon during checkout. This identifies a meaningful behaviour, but does not specify which coupon, cart or outcome to check.
Case: with an eligible item costing ₹500 and no other charges or discounts, apply a valid ₹50 coupon. Expect a ₹450 total and a ₹50 discount in the order summary. These amounts are illustrative test data, not a claim about a real store.
A separate case uses an expired coupon and expects a rejection with the total unchanged. Another removes an accepted coupon and expects the original total to return. Do not hide these different outcomes behind one vague “coupon works” result.
How to answer in an interview
A scenario names a behaviour or flow we want to cover, while a test case specifies conditions, data and an expected result for a particular check. “Apply a coupon” is a scenario; checking that an expired coupon leaves the total unchanged is a case. Several cases can cover one scenario. Teams sometimes use scenario to mean a detailed executable example, so I confirm the local convention.
Common confusion
A test case does not need a long click-by-click script if its setup, action and observable result are clear. Conversely, “works correctly” is not an adequate expected result. Record assumptions about taxes, fees and eligibility before comparing totals.
Likely follow-up: Where do boundary values fit? They become cases under the relevant scenario, such as testing a minimum cart amount just below, at and above its threshold.
This is independent foundation-level learning material, not affiliated with ISTQB.
Quick answers
Is a scenario always end-to-end?
No. It can describe a whole journey or a smaller behaviour. Its scope should be explicit.
Can an automated test be a test case?
Yes. Executable setup, actions and assertions can express the same information as a written case.
Sources
Want a project you can show in interviews?
The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.