UI Automation
Playwright Lab: UI Automation Sprint
Ship stable browser tests with Playwright, from selectors to trace viewers.
Remote lab Intermediate Playwright
6 weeks · 22 live hours
KRW 980,000 · informational reference
What happens inside
You will stand up a small but real suite against a sample retail app, then graduate to refactoring flaky areas with fixtures, projects, and parallel shards. We emphasize readable locators, deterministic waits, and CI-friendly reporters rather than sheer test count.
Included cadence
- ↗ Starter repo with GitHub Actions skeleton
- ↗ Locator strategy decision tree laminate
- ↗ Trace + HTML report walkthrough clinics
- ↗ Fixture patterns for auth and multi-role flows
- ↗ Mentored code review on your final suite
- ↗ Assignment on quarantining unstable cases
- ↗ Night shift friendly async Q&A window
Outcomes you can audit
Maintain a twelve-case Playwright suite with shared fixtures.
Explain when to prefer role+name locators over CSS.
Attach traces to bug tickets your team would accept.
Straight answers
Hardware expectations?
16 GB RAM recommended for local headed runs; you can opt for CI-only runs if your laptop is thin.
Limitations?
We do not cover native mobile drivers; browser and emulated viewports only.
Team discount?
Three seats or more unlocks a private retrospective session on your repo.
Participant notes
“Finally someone showed why my waits were lying. The Playwright Lab assignment on the flaky checkout flow mirrors what I fight weekly—specific, not generic.”
“Peer review caught an assert that would have masked a layout bug. Worth the late sessions.”