This capstone lesson brings everything together and points you toward next steps. By now, you have seen how to design, implement and operate Playwright suites in realistic engineering environments.
Capstone Project Brief
Design a Playwright test suite for a demo e-commerce or SaaS app that includes fixtures, page models, network checks, accessibility scans, visual tests and CI integration.
Capstone requirements (suggested):
- At least 2 critical user journeys covered end to end
- Page models for key screens (login, dashboard, checkout)
- Fixtures for auth and common data
- Network assertions for at least one API
- a11y checks on 2–3 important pages
- Visual tests for selected components
- CI pipeline with parallelism, retries and trace artifactsFor next steps, consider exploring advanced topics like component testing, performance profiling around tests, or contributing improvements back to your organisation’s shared Playwright tooling.
Common Mistakes
Mistake 1 — Treating the capstone as a one-off exercise
This limits learning.
❌ Wrong: Completing the project and never revisiting or iterating on it.
✅ Correct: Use it as a foundation to experiment with new patterns and tools.
Mistake 2 — Ignoring feedback from others
This slows growth.
❌ Wrong: Building in isolation without reviews.
✅ Correct: Invite reviews from developers, testers and even designers.