Typorithm learning path
QA: automation with Playwright
Build dependable unit, API and browser tests, isolate data, investigate failures and prepare a bounded CI run. Prerequisites: QA foundations and TypeScript foundations. Reviewed 5 November 2026 with Playwright 1.64.1. Start with one assertion; advanced extensions are optional.

Study with a practical destination
Use the linked lessons in order, complete the lab and explain the decisions without the reference. Select the path and depth that match your role.
QA: from useful cases to dependable automation
Before starting: Start with the QA foundations. Before automation, practise TypeScript functions, arrays, promises and unknown input; basic HTTP helps. Browser test execution requires a computer; lessons and self-checks are available in the app.
Build and explain: Turn a clear requirement into boundary, state, API and SQL checks, then implement isolated browser tests with explicit expected results.
- 1. 1. Quality, risk and independent evidence
- 2. 2. Acceptance criteria and requirement review
- 3. 4. Boundary values and comparison mistakes
- 4. 10. Authentication, ownership and account isolation
- 5. 13. Joins, zero counts and cardinality
- 6. 16. Capstone: investigate a small role catalogue
- 7. 9. Generics, constraints and preserved relationships
- 8. 1. Runtime decoding at an API boundary
- 9. 1. A test runner and assertions that can fail
- 10. 5. API integration and stored postconditions
- 11. 6. Browser locators and meaningful visible results
- 12. 10. Browser contexts and authenticated state
- 13. 12. Accessibility, keyboard use and layout evidence
- 14. 16. Capstone: a verified local role workflow
Review evidence: Attempt the small task before reading the solution. Show that a deliberately wrong AND/OR implementation fails, repeat saves without duplication, keep two accounts isolated, and explain a trace. Optional stretches are not prerequisites; use the capstones for a practical review.
Your learning path
0 of 16 lessons completed
Saved on this device
Module 1 · 1 lessons
1. A test runner and assertions that can fail
Run a small test with an independently chosen expected result.
Module 2 · 1 lessons
2. Parameterized unit cases and boundary evidence
Turn a small behavior table into readable regression tests.
Module 3 · 1 lessons
3. Fakes, mocks and a real integration seam
Control one dependency without proving only that a mock returns its setup.
Module 4 · 1 lessons
4. Property and metamorphic checks with concrete anchors
Check relationships across inputs without losing an independent example oracle.
Module 5 · 1 lessons
5. API integration and stored postconditions
Exercise the real local HTTP boundary and inspect the effect of a command.
Module 6 · 1 lessons
6. Browser locators and meaningful visible results
Find controls by their accessible purpose and verify the selected subset.
Module 7 · 1 lessons
7. Auto-waiting, assertions and readiness
Wait for the required observable state instead of guessing a delay.
Module 8 · 1 lessons
8. Form validation and keyboard behavior
Verify input boundaries and accessible feedback through real controls.
Module 9 · 1 lessons
9. Network failures, clocks and deterministic recovery
Control one asynchronous condition and assert the resulting user-visible state.
Module 10 · 1 lessons
10. Browser contexts and authenticated state
Keep cookie ownership and account state explicit in browser tests.
Module 11 · 1 lessons
11. Fixtures, cleanup and parallel isolation
Make setup and teardown explicit without deleting another test’s data.
Module 12 · 1 lessons
12. Accessibility, keyboard use and layout evidence
Combine automated findings with explicit manual and interaction limits.
Module 13 · 1 lessons
13. Flaky tests, traces and reproducible failures
Investigate inconsistent outcomes instead of converting them into silent passes.
Module 14 · 1 lessons
14. CI, bounded workers and safe artifacts
Make the verification sequence explicit without installing a workflow into production.
Module 15 · 1 lessons
15. Bounded concurrency and latency evidence
Measure the chosen workload without pretending a small lab proves production capacity.
Module 16 · 1 lessons
16. Capstone: a verified local role workflow
Connect browser actions, API postconditions and account isolation in one small project.