Test Design for Quality Assurance (QA)s
Test design is the skill of choosing and writing tests that find the most defects with the fewest cases. It uses techniques such as equivalence partitioning and boundary value analysis, turns them into clear test cases, organises them in plans and strategies, and adds exploratory sessions guided by heuristics.
Stage: Testing Fundamentals · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Test Design
- Apply equivalence partitioning and boundary value analysis to an input field
- Build a decision table for rules that combine several conditions
- Write a test case with preconditions, steps, data and expected result
- Draft a test plan with scope, risks, entry and exit criteria
- Run a time-boxed exploratory session using a charter
- Use heuristics such as SFDIPOT to prompt new test ideas
Test Design interview questions
How would you test a field that accepts ages 18 to 60?
Use boundary value analysis: test 17, 18, 19, 59, 60 and 61, plus an invalid class such as letters, empty, negative and a very large number. Equivalence partitioning gives three groups, below, within and above range, with one or two values from each.
What is the difference between a test plan and a test strategy?
A strategy is a high-level, long-lived approach describing test levels, tools and risk handling for an organisation or product. A plan is project-specific: it covers scope, schedule, resources, environments and exit criteria for a particular release.
Where Test Design fits in the Quality Assurance (QA) roadmap
Test Design belongs to the Testing Fundamentals stage (beginner level), which takes about 7 hours. Think like a tester.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap