Knowing what to learn is half the battle; doing it week by week is the other half. This plan gives you 12 weeks of Playwright assignments, each building on the last, plus learning paths by role so you can skip what you already know. For the full stage-by-stage career view, see the Playwright roadmap.
Learning Roadmaps & Role Definitions
Structured paths through this course, mapped to modules and projects. Pick the pace that fits you; each milestone ends with something you can show.
30-Day Roadmap — “Job-ready fundamentals”
Goal: write reliable UI tests and a basic POM framework. Target level: Fresher → early 1yr.
Week 1 — Foundations - Modules 1–6 (testing, automation, TS basics, Playwright intro, setup, first test) - Deliverable: environment set up; 3 passing tests on saucedemo.
Week 2 — Core interactions - Modules 7–16 (locators, context/page, actions, assertions, elements, waits, forms, dropdowns, checkboxes, dialogs) - Deliverable: forms + validation suite.
Week 3 — More interactions + runner - Modules 17–22 (frames, tabs, mouse/keyboard, screenshots, tracing, test runner) - Deliverable: Project 1 (Beginner Demo Suite) complete.
Week 4 — POM + fixtures - Modules 23–29 (fixtures, hooks, config, projects, tags, data, POM) - Deliverable: Project 2 (E-commerce POM Framework) complete + on GitHub.
60-Day Roadmap — “Framework capable”
Continue from Day 30. Target level: 1–2yr SDET.
Week 5 — Advanced POM + utilities + API - Modules 30–33 (advanced POM, utilities, API testing, UI+API) - Deliverable: API CRUD spec + one UI+API integration test.
Week 6 — Auth, network, mocking - Modules 34–36 (storageState auth, network interception, mocking) - Deliverable: storageState login-once; mocked error/empty states.
Week 7 — Tricky UI + cross-browser + parallel - Modules 37–45 (upload/download, tables, dates, dynamic, shadow DOM, iframes, cross-browser, parallel) - Deliverable: cross-browser run (chromium/firefox/webkit).
Week 8 — Reliability + Git + CI - Modules 46–53 (retries, flaky tests, reports, logging, Git, CI/CD, Jenkins, GitHub Actions) - Deliverable: Project 3 (Full Framework) with sharded GitHub Actions CI.
90-Day Roadmap — “Senior-ready”
Continue from Day 60. Target level: 2–3yr → Senior SDET.
Week 9 — Docker + environments - Modules 54–55 (Docker, environment management) - Deliverable: suite runs in the Playwright Docker image; multi-env via TEST_ENV.
Week 10 — Architecture + patterns - Modules 56–57 (framework architecture, design patterns) - Deliverable: refactor to the layered enterprise architecture; add Factory/Strategy/Facade.
Week 11 — Enterprise + best practices - Modules 58–59 (enterprise framework, best practices) - Deliverable: Project 4 (Enterprise UI+API Suite) with Jenkins.
Week 12 — Interview + troubleshooting + capstone - Modules 60–62 (interview prep, troubleshooting, capstone) - Deliverable: begin Project 5 (Automation Platform); complete interview banks; do 2 mock interviews.
6-Month Roadmap — “Architect track”
A slower, deeper pace with mastery and portfolio depth. Target level: 3–5yr / Architect.
- Month 1: Modules 1–22 + Project 1. Solidify fundamentals; write daily.
- Month 2: Modules 23–36 + Project 2. POM, fixtures, API, auth, mocking.
- Month 3: Modules 37–50 + Project 3. Tricky UI, cross-browser, parallel, reports, Git/CI.
- Month 4: Modules 51–55 + Docker/env mastery. Project 4 started.
- Month 5: Modules 56–59 + patterns/architecture. Project 4 complete; Project 5 started.
- Month 6: Modules 60–62 + Project 5 complete. Interview banks, mock interviews, portfolio polish, and (optional) visual/a11y/component testing extensions.
By month 6 you should have: 5 public repos with green CI + reports, fluency across all 62 modules, and confident answers to the scenario bank.
Role Definitions (what each level means)
Fresher / QA Automation Engineer (0–1y) - Writes UI tests with good habits (semantic locators, web-first assertions). - Understands POM at a basic level; runs tests locally and reads reports. - Signals: Projects 1–2, Fresher interview bank fluency.
SDET (1–2y) - Builds POM + fixtures frameworks; does API testing and UI+API integration. - Uses storageState, tags, data-driven tests; contributes to CI. - Signals: Project 3, 1–2yr bank.
SDET (2–3y) - Designs framework structure; debugs flakiness; runs parallel/sharded suites. - Handles auth strategies, network/mocking, cross-browser, multi-env. - Signals: Project 4, 2–3yr bank + scenarios.
Senior SDET (3–4y) - Owns architecture and reliability; designs CI/CD; mentors; makes trade-offs. - Containerizes; adds DB/visual/a11y verification where valuable. - Signals: Project 4/5, senior bank, leadership stories.
Automation Architect / Lead (5y+) - Designs platforms adopted across teams; sets standards and governance. - Optimizes at scale; owns observability, patterns, and shared modules. - Signals: Project 5, architect bank, system-design fluency, measurable org impact.
Daily/Weekly rhythm (recommended)
- Daily: 1–2 modules read + code every example yourself (don’t just read).
- Weekly: one project milestone; push to GitHub; write a short “what I learned.”
- Every 2 weeks: one mock interview (rotate levels) + review your flakiness/reliability habits.
Weekly Assignments (12 Weeks)
Hands-on assignments to cememnt each week of the 90-day roadmap. Each has a task and acceptance criteria. Do them in your own repo and push after each week.
Week 1 — Setup & first tests
Task: Set up the environment; write 5 tests on saucedemo (valid/invalid/locked login, product count, add-to-cart). Acceptance: All pass headless; HTML report opens; a forced failure produces a screenshot.
Week 2 — Interactions
Task: Automate a form with validation (3 negative + 1 positive), a native + custom dropdown, and checkboxes/radios. Acceptance: Each asserts the resulting state; no waitForTimeout anywhere.
Week 3 — Tricky UI + evidence
Task: Handle a dialog, an iframe, a new tab, and a hover menu; enable trace retain-on-failure. Acceptance: Open a trace of a deliberately failed test and identify the failing step. Project 1 complete.
Week 4 — POM + fixtures
Task: Refactor Weeks 1–3 into LoginPage/InventoryPage/CartPage/CheckoutPage + a fixtures file; data-drive login from JSON; tag @smoke/@regression. Acceptance: Changing one locator touches only its page class. Project 2 complete + on GitHub.
Week 5 — API + integration
Task: Write GET/POST/PUT/DELETE against a public API with chaining; add one UI+API integration test (seed via API, verify in UI). Acceptance: Status + body asserted; one JSON-schema validation included.
Week 6 — Auth + mocking
Task: Implement storageState login-once via a setup project; mock an empty state and a 500 error via route.fulfill. Acceptance: Tests skip UI login; mocked states pass deterministically.
Week 7 — Cross-browser + parallel
Task: Add firefox/webkit projects and a mobile project; make a data-colliding test, then fix it with unique data; run --workers=4. Acceptance: Green on 3 browsers; the previously colliding test passes in parallel.
Week 8 — Reliability + CI
Task: Add retries (CI-only) + trace: 'on-first-retry'; create a GitHub Actions workflow with 2–3 shards + merged HTML report. Acceptance: CI runs sharded and publishes a merged report artifact. Project 3 complete.
Week 9 — Docker + environments
Task: Write a Dockerfile (pinned Playwright image) and run the suite in the container; add dotenv keyed by TEST_ENV with .env.qa/.env.uat + a required-var validator. Acceptance: Suite runs in Docker; switching TEST_ENV changes the target with no code edits.
Week 10 — Architecture + patterns
Task: Restructure into the layered enterprise architecture; implement a Factory, a Builder, and UI/API LoginStrategy classes. Acceptance: One spec demonstrates factory data + ApiLogin; a login spec uses UiLogin.
Week 11 — Enterprise + best practices
Task: Add ESLint/Prettier/strict tsconfig; add a simple custom reporter (summary line); audit a spec against Module 59 and fix all violations. Acceptance: Lint passes in CI; the audited spec has zero hard waits/brittle locators/misplaced assertions. Project 4 complete.
Week 12 — Capstone + interviews
Task: Start Project 5 (Docker compose app + tests + DB verification); complete all interview banks; do 2 recorded mock interviews (one coding, one design). Acceptance: A DB-verification test passes in compose; you can whiteboard the Project 5 architecture in under 5 minutes.
- ✅ Green tests, no hard waits, semantic locators
- ✅ Pushed to GitHub with a README note
- ✅ Could explain every line you wrote
- ✅ Wrote a 3-sentence “what I learned / what was hard”
FAQs
Can I learn Playwright in 12 weeks?
Yes, with steady practice of an hour or two a day you can reach framework-building level in about 12 weeks, faster if you already know Selenium or JavaScript.
