Design a Playwright Checkout Test Suite That Blocks Bad Merges
Overview
What this challenge is about.
Design a Playwright Checkout Test Suite That Blocks Bad Merges. Intermediate challenge in design. Designing real products under real constraints, earn a bloc...
The Brief
What you'll do, and what you'll demonstrate.
Design an end-to-end test suite that converts a manual, ad-hoc checkout quality pass into an automated gate that blocks any merge which regresses the seven highest-risk checkout journeys.
This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
Earning criteria — what you'll demonstrate
- Translate production incident data into a prioritized, risk-ranked test coverage plan
- Apply the Page Object Model to design end-to-end tests that survive user-interface refactors
- Design a continuous-integration gate that blocks regressions without slowing pull requests
- Justify test reliability and runtime trade-offs (sharding, retries, seeding) in writing
- Communicate a test strategy clearly enough that another engineer can build from it unaided
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- End To End Testing
Apply end to end testing to solve real industry problems and demonstrate production-level capability.
- Playwright
Apply playwright to solve real industry problems and demonstrate production-level capability.
- Ci Cd
Apply ci cd to solve real industry problems and demonstrate production-level capability.
- Page Object Model
Apply page object model to solve real industry problems and demonstrate production-level capability.
- Test Strategy
Apply test strategy to solve real industry problems and demonstrate production-level capability.
- Github Actions
Apply github actions to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Quality / Test Automation Engineer
Designing a risk-ranked Playwright suite that gates merges is the core of automation engineering: you turn incident data into coverage, harden tests against flakes, and own the quality gate that protects revenue-critical flows.
This challenge sharpens
- end-to-end-testing
- playwright
- test-strategy
Software Engineer in Test
This challenge mirrors the daily work of an SDET: building maintainable test architecture with the Page Object Model, wiring suites into pipelines, and writing the strategy docs that let a whole team contribute tests confidently.
This challenge sharpens
- page-object-model
- test-strategy
- end-to-end-testing
Continuous-Integration / DevOps Engineer
Wiring a sharded, sub-12-minute required check into GitHub Actions is foundational DevOps work, bridging you toward owning pipelines, build gates, and the feedback loops that keep deployments safe and fast.
This challenge sharpens
- ci-cd
- github-actions
- playwright