Skip to content
L-SYSTEM

recommendedintermediate

Playwright Test Automation for QA Engineers

A full working course on Playwright with TypeScript for QA engineers in large professional-services firms (Big 4 and similar). It covers the same ground as a comprehensive "zero to hero" Playwright curriculum: TypeScript essentials for test code, installation and project layout, running and debugging (CLI, UI mode, Inspector, codegen, Trace Viewer), locators and the strictness rule, web-first assertions, auto-waiting and the timeout hierarchy, every common UI component (inputs, checkboxes, radios, dropdowns, tooltips, dialogs, tables, date pickers, sliders, iframes), the Page Object Model and a scalable page architecture, custom fixtures, configuration and projects, environment variables and mobile emulation, authentication reuse through storageState, artifacts and reporters, visual regression testing, API requests, network interception and mocking, parallelism, retries, tags and flakiness control, Docker and CI on GitHub Actions. Every topic is taught the same way: the problem that exists without the feature, the feature that solves it, and the price you pay for using it. The course is written for people who will maintain a suite on a client engagement for years, not for people writing a demo test once — so review criteria, evidence for audit, secret handling and cost of maintenance are part of the material, not an appendix. By the end you should be able to build and maintain a Playwright suite unaided, and to pass an external certification-style exam on the same syllabus.

Path through the course · 27 units

any order · units can be taken in any order you likeView: map · steps

ANY

0 / 1

2 OF 3

0 / 2

3 OF 5

0 / 3

final

Exam

closed

The path in words
  • Stage 1 · Why Playwright, and what it actually does — can start; ~1 h
  • Stage 2 · The TypeScript you actually need for test code — can start; ~1.5 h
  • Stage 2 · Installing Playwright and laying out the project — can start; ~1 h
  • Stage 3 · Running and debugging: CLI, UI mode, Inspector, codegen, Trace Viewer — can start; ~1.5 h
  • Stage 4 · The anatomy of a test: describe, hooks, steps, annotations — can start; ~1 h
  • Stage 5 · Locator syntax: CSS, text, XPath and chaining — can start; ~1 h
  • Stage 6 · User-facing locators and the strictness rule — can start; ~1.5 h
  • Stage 7 · Filtering, relationships and lists of elements — can start; ~1 h
  • Stage 7 · Assertions and extracting values — can start; ~1.5 h
  • Stage 8 · Auto-waiting and the timeout hierarchy — can start; ~1.5 h
  • Stage 8 · Text inputs, keyboard and mouse — can start; ~1 h
  • Stage 9 · Checkboxes, radios, dropdowns and tooltips — can start; ~1.5 h
  • Stage 9 · Dialogs, alerts and web tables — can start; ~1.5 h
  • Stage 9 · Date pickers, sliders and iframes — can start; ~1.5 h
  • Stage 9 · Page Object Model: the first objects — can start; ~1.5 h
  • Stage 9 · Evidence: screenshots, video, traces and reporters — can start; ~1 h
  • Stage 9 · API requests with Playwright — can start; ~1.5 h
  • Stage 10 · Page architecture: base helpers and a page manager — can start; ~1.5 h
  • Stage 10 · Visual regression testing — can start; ~1 h
  • Stage 10 · Network interception and mocking — can start; ~1.5 h
  • Stage 11 · Fixtures: built-in, custom, and worker-scoped — can start; ~1.5 h
  • Stage 12 · Configuration, projects, environments and mobile emulation — can start; ~1.5 h
  • Stage 13 · Authentication once: setup projects, storageState and API login — can start; ~1.5 h
  • Stage 13 · Parallelism, retries, tags and flakiness — can start; ~1.5 h
  • Stage 14 · Docker and continuous integration — can start; ~1.5 h
  • Stage 15 · Confusion pairs and exam readiness — can start; ~1.5 h
  • Stage 15 · Delivery practice: strategy, review and evidence on an engagement — can start; optional; ~1.5 h

Programme · 27 units

1Why Playwright, and what it actually does

Explain the two failure modes of legacy UI automation — timing flakiness and driver overhead — and how Playwright's architecture removes each

~1 hcan start
2The TypeScript you actually need for test code

Read and write the JavaScript constructs that appear in every Playwright test: const/let, arrow functions, template literals, destructuring, objects and arrays

~1.5 hcan start
3Installing Playwright and laying out the project

Install Playwright into a new repository and into an existing front-end repository without breaking either

~1 hcan start
4Running and debugging: CLI, UI mode, Inspector, codegen, Trace Viewer

Run the suite, a file, a single test and a tagged subset from the command line

~1.5 hcan start
5The anatomy of a test: describe, hooks, steps, annotations

Structure a spec file with describe blocks and the four hooks, and say when each hook runs relative to workers

~1 hcan start
6Locator syntax: CSS, text, XPath and chaining

Read the DOM vocabulary a locator depends on: tag, attribute, class, id, text node, parent and child

~1 hcan start
7User-facing locators and the strictness rule

Apply the locator priority order: role, label, placeholder, text, alt, title, test id, CSS or XPath last

~1.5 hcan start
8Filtering, relationships and lists of elements

Use filter() with hasText, hasNotText, has and hasNot to narrow a set by content or by a descendant

~1 hcan start

Show the remaining 19 units