Test Design Techniques
Find the gaps in a spec before any code is written, then turn rules into a short list of test values that each mean something: equivalence partitions, boundary values, decision tables, state transitions and pairwise combinations, all worked on the real forms and rules of the Shelf practice shop. For learners who know what a test, a bug report and a user story are. Course 3 of the QA Engineer Path.
Course 3 of 13 in the QA Engineer Path
8 lessons · 110 stepscertificate
8 lessons · 110 steps
certificateWhat you will learn
Find gaps in a spec and derive test values with partitions, boundaries and decision tables.
Course program
The full outline. Lessons open when the course does.
Requirements before code
What makes a requirement testable13 steps
Reviewing a spec before code13 steps
Values for one field
Equivalence partitioning12 steps
Boundary value analysis15 steps
Rules, states and combinations
Decision tables14 steps
State transitions14 steps
Pairwise testing14 steps
Review: the registration page15 steps
How this course compares with others
Section: QA Engineer Path
- Software Testing from Zero: The First Shift8 lessonscertificate
- How Software Gets Built: Process for Testers7 lessonscertificate
- Test Design Techniquesyou are here8 lessonscertificate
- Test Cases, Bug Reports and Test Plans13 lessonscertificate
- Web Testing with DevTools13 lessonscertificate
- API Testing with Postman12 lessonscertificate
- Databases and SQL for Testers8 lessonscertificate
- Mobile Testing and Traffic Interception12 lessonscertificate
- Command Line and Git for Testers8 lessonscertificate
- Logs, Metrics and Queues for Testers10 lessonscertificate
- Environments, Docker and CI for Testers9 lessonscertificate
- AI Assistants for Testers5 lessonscertificate
- Release Night: Test a Shop End to End10 lessonscertificate
Next on the path: Test Cases, Bug Reports and Test Plans
The author
Artsiom Rusau – QA engineer and course author. He has tested software since 2019 and has taught software testing since 2020.