A corner case is a situation that only happens when several specific, unusual conditions occur at the same time. It differs from an edge case, which tests a single condition at its extremes.
Why it matters: Corner cases are easy to dismiss as rare, but they can turn out to happen often in real use. Judging how rare they really are depends on understanding the system and how people use it.
In practice: Testers ask “what if?” about combinations of conditions, especially near the end of development, and challenge assumptions that a scenario won't happen. When a gut feeling says something is risky, they look for evidence rather than accepting a quick reassurance.
Examples:
- A failure that only appears when a large import runs during a scheduled backup.
- A scenario labelled rare early in a project that customers hit daily after launch.
Common pitfalls:
- Labelling scenarios as corner cases without data on how often they happen.
- Accepting “no one would do that” without checking.
What's the difference between an edge case and a corner case? An edge case pushes one condition to its limit, such as the maximum input length. A corner case combines several unusual conditions at once.
