Foundation → Build a Playwright Framework with Automation Tech Guru

Phase 1 — Foundation

Self-paced · 5 Days

What this phase is: A complete, standalone introduction to writing and running real Playwright tests. Nobody needs anything beyond this to say "I can automate a browser."

By the end, you’ll walk away with: A handful of independent, working Playwright test scripts you wrote and ran yourself.

Where this naturally leads: These scripts are real, but they're separate files — nothing shared between them, no reusable structure, and nothing that touches an API yet. The moment you want to test more than a handful of pages, or need your UI and API checks to work together, you're describing framework design — which is exactly what Phase 2 builds.

Phase 2 — Build a Playwright Framework

· Live Cohort · 11 Days

What this phase is: The heart of the program, turning individual scripts into a real, structured, production-style automation framework — the thing an actual QA/SDET role expects you to build.

By the end, you’ll walk away with: A GitHub repo containing a real Playwright + TypeScript framework — Page Object Model, fixtures, UI tests, API tests — built and reviewed live.

Where this naturally leads: This framework works — on your machine, when you run it yourself. It doesn't yet run automatically when code changes, and nothing about it is visible to a team the way a real engineering workflow is. Making that happen automatically, safely, and repeatedly is a CI/CD problem — which is what Phase 3 solves.

Keywords: "Playwright", "Playwright interview questions", "Playwright C#", "Playwright .NET", "Selenium", "Selenium to Playwright", "API automation", "API automation testing", "QA automation", "SDET interview", "automation testing interview", "QA mentorship"