intermediate · cohort · 7 weeks · 9–11 hrs/week
Playwright Cross-Browser Lab
Model user journeys across Chromium, Firefox, and WebKit with trace files your team can replay.
¥92,000 JPY — informational list price
Overview
You configure projects, trace viewer workflows, and storage state to avoid repetitive logins. Exercises emphasize deterministic waits and avoiding sleep-heavy scripts that hide timing bugs.
What is included
- Project matrices for desktop and mobile emulation
- Trace viewer walkthroughs for triage handoffs
- Storage state patterns for SSO-heavy apps
- API hooks for seeding data safely
- Parallel shard planning for slower suites
- Codegen usage without letting it own your style
- PDF snapshot discipline for audit-heavy teams
Outcomes you can evidence
- Produce traces that shorten bug conversations with developers
- Maintain a Playwright config readable by the next hire
- Choose project splits that keep CI under budget
Lead mentor
Builds browser automation curricula for teams migrating off legacy stacks.
Avatars load from ui-avatars.com with a styled fallback if blocked.
FAQ
Some patterns apply, but API Contract Testing Sprint is a better fit if browsers are out of scope.
Experience notes
“Trace files from Playwright Cross-Browser Lab exercises became our default attachment when Jira tickets looked vague.”
“Codegen section was short — appreciated that — but I wanted one more multi-project failure scenario.”