Zum Inhalt springen
L-SYSTEM

empfohlenMittelstufe

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.

Ihre Lektion ist in Ihrer Sprache: Ihr Assistent leitet sie.

  • Material: Englisch
  • Prüfung: Englisch – wird auf der Website abgelegt, nicht übersetzt
So funktioniert’s

Ihr Assistent holt das Kursmaterial von unserem Server und leitet die Lektion in Ihrer Sprache.

Die Prüfung wird auf der Website abgelegt, ohne Assistenten. Prüfungsfragen werden nicht übersetzt: Das ist für jeden Kurs so festgelegt.

So verbinden Sie einen Assistenten

Weg durch den Kurs

· 27 Einheiten

freie Reihenfolge · die Stufen unten sind die vom Autor vorgeschlagene Reihenfolge, keine BedingungAnsicht: Karte · Stufen

  1. Stufe 1

    ~1,2 Std.

  2. Stufe 2

    ~2,9 Std.

    Core · laut Plan des Autors nach „Why Playwright, and what it actually does“

  3. Stufe 3

    ~1,8 Std.

  4. Stufe 4

    ~1,2 Std.

  5. Stufe 5

    ~1,2 Std.

  6. Stufe 6

    ~1,7 Std.

  7. Stufe 7

    ~2,9 Std.

    Core · laut Plan des Autors nach „User-facing locators and the strictness rule“

  8. Stufe 8

    ~3 Std.

  9. Stufe 9

    ~9,8 Std.

  10. Stufe 10

    ~4,7 Std.

  11. Stufe 11

    ~1,8 Std.

  12. Stufe 12

    ~1,7 Std.

  13. Stufe 13

    ~3,5 Std.

    laut Plan des Autors nach „Configuration, projects, environments and mobile emulation“

  14. Stufe 14

    ~1,7 Std.

    • 25 · Scale · laut Plan des Autors nach 2 davon: „Authentication once: setup projects, storageState and API login“, „Evidence: screenshots, video, traces and reporters“, „Parallelism, retries, tags and flakiness“

      Docker and continuous integration

      ~1,7 Std.

  15. Stufe 15

    ~3,4 Std.

    Review

  16. Prüfung

    gesperrt · in den Kurs einschreiben

    • Abschluss · im Browser, ohne den Assistenten

      Prüfung

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

Lehrplan · 27 Einheiten

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,2 Std.
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,7 Std.
3Installing Playwright and laying out the project

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

~1,2 Std.
4Running and debugging: CLI, UI mode, Inspector, codegen, Trace Viewer

Run the suite, a folder, a file, a single test, a project, the last failures and only the tests affected by a change from the command line

~1,8 Std.
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,2 Std.
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,2 Std.
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,7 Std.
8Filtering, relationships and lists of elements

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

~1,2 Std.
9Assertions and extracting values

Distinguish web-first assertions from generic ones and default to the former

~1,7 Std.
10Auto-waiting and the timeout hierarchy

List the actionability checks and explain which action requires which of them

~1,8 Std.
11Text inputs, keyboard and mouse

Choose between fill, clear and pressSequentially by the events each one sends, and say when character-by-character typing is required

~1,2 Std.
12Checkboxes, radios, dropdowns and tooltips

Use check, uncheck and setChecked correctly, and justify force: true on a visually hidden native input

~1,7 Std.
13Dialogs, alerts and web tables

Explain what Playwright does with a native dialog when no listener is registered, and what a registered listener is obliged to do

~1,7 Std.
14Date pickers, sliders and iframes

Automate a date picker by typing where possible and by navigating the calendar where not

~1,8 Std.
15Page Object Model: the first objects

State the specific duplication a page object removes and the specific change it makes cheap

~1,7 Std.
16Page architecture: base helpers and a page manager

Extract shared behaviour into a shallow base class — one level of inheritance — and use composition beyond that

~1,7 Std.
17Fixtures: built-in, custom, and worker-scoped

Name the built-in fixtures and say what each provides, and explain where testInfo comes from (it is not a fixture)

~1,8 Std.
18Configuration, projects, environments and mobile emulation

Use projects to run the same tests across browsers, devices, roles and ENGAGE environments, and cap a project's parallelism with its own workers setting

~1,7 Std.
19Authentication once: setup projects, storageState and API login

Build a setup project that authenticates once and saves the session to storageState, including IndexedDB when the identity library keeps tokens there

~1,7 Std.
20Evidence: screenshots, video, traces and reporters

Capture screenshots of the page, of an element and into a buffer, and attach them to the report

~1,3 Std.
21Visual regression testing

Write a screenshot comparison with toHaveScreenshot and manage baselines with the updateSnapshots modes and path templates

~1,3 Std.
22API requests with Playwright

Use the request fixture to write API tests, asserting with await expect(response).toBeOK() and on headers and body

~1,7 Std.
23Network interception and mocking

Choose between fulfill, continue, abort and fallback for an intercepted request, and explain handler order

~1,8 Std.
24Parallelism, retries, tags and flakiness

Explain what a worker is, how work is split with and without fullyParallel, and the default number of workers

~1,8 Std.
25Docker and continuous integration

Run the suite in the official Playwright image with the recommended Docker flags, and keep the image tag equal to the installed Playwright version

~1,7 Std.
26Confusion pairs and exam readiness

Separate the pairs of Playwright concepts that are most often confused, by naming the one rule that divides each pair

~1,7 Std.
27Delivery practice: strategy, review and evidence on an engagement

Decide what to automate and at which level — unit, API, UI, visual, accessibility, journey — and defend the decision to a client

~1,7 Std.