Playwright
Welcome, champion! 🔥
You've mastered 0 of 70 lessons. Start your first lesson free — no signup needed.
About this course
Playwright can drive Chromium, Firefox and WebKit from one test suite, wait for elements on its own and record a trace of every failure. Yet many teams still write Playwright tests the old way, with element handles, fixed timeouts and assertions that do not retry, and then wonder why the suite is flaky. This online Playwright course on Abekus teaches Playwright Test with TypeScript the way the current documentation recommends, in short reading-card lessons each followed by an MCQ quiz.
Who this Playwright course is for
It is written for QA engineers, SDETs and web developers who want cross-browser end-to-end tests in TypeScript. You should know basic JavaScript or TypeScript, including async and await; no Playwright experience is needed. By the end you can write tests with role-based locators and web-first assertions, structure suites with fixtures and projects, sign in once and reuse the state, mock or call APIs, debug failures with traces, and scale runs with workers, retries and sharding.
Examples follow one setup: @playwright/test 1.65.1 with TypeScript on Node.js 24 LTS, the chromium, firefox and webkit browsers installed with npx playwright install, and configuration in playwright.config.ts using defineConfig and devices. Every lesson tests the same small store, ShopLite, at http://localhost:3000, started by the webServer option, so locators, fixtures and sign-in setup carry from one topic to the next. Code blocks are TypeScript only and stay short. The course leaves out Playwright for Python, Java and .NET, experimental component testing and the test agents beyond a mention, library-mode automation and scraping, and screenshots of the UI mode, trace viewer or HTML report.
How the lessons work
Each lesson is a short set of reading cards on one feature, usually with a short test and what the run reports, followed by a quiz of multiple-choice questions. Many questions ask what a test will do, such as which element a locator matches or whether an assertion retries. Lessons start with a first test and how Playwright drives browsers, then cover locators, actions and web-first assertions, test structure and fixtures, configuration and projects, authentication and network control, API testing, debugging and reports, visual comparisons and scaling test runs in CI. You move at your own pace and earn a certificate when you finish.
MCQ practice vs video courses for Playwright
Video courses on Udemy, Coursera or YouTube suit learners who want to watch a suite being recorded and run in an editor. This course is built for a different job: a short explanation followed straight away by questions about real tests, such as whether a locator is strict, what the default expect timeout is, whether tests in one file run in parallel by default, or why expect(await locator.textContent()) does not retry. Playwright rewards precise knowledge of these defaults, and predicting them question by question is what removes guesswork from a failing run. Many testers use both: a video for a first walkthrough, and questions for the detail.
Common Playwright mistakes
The course corrects these directly:
- Finding elements with page.$() and element handles. Locators such as page.getByRole(...) are the recommended way.
- Adding page.waitForTimeout(3000) before a click. Actions auto-wait; assert with web-first assertions instead.
- Thinking the default test timeout is five seconds. A test gets 30 seconds; an expect gets five.
- Expecting tests inside one file to run in parallel by default. Files run in parallel; tests in a file run in order.
- Writing expect(await locator.textContent()).toBe('2'). Use await expect(locator).toHaveText('2'), which retries.
- Running Playwright 1.65 on Node.js 18 or 20. Its system requirements list Node.js 22, 24 or 26.
- Assuming the chromium browser is the open-source Chromium build. Since 1.57 it uses Chrome for Testing.
Best way to learn Playwright
Start with one user journey in one browser, then widen it. Use getByRole first and fall back to test ids or CSS only when needed, let web-first assertions do the waiting, and sign in once in a setup project. Turn on traces for retries so every failure comes with evidence. The final part of the course is built around these choices: Playwright against Cypress and Selenium, locators against element handles, choosing a locator, UI or API setup and what to mock, and worked cases including a cart flow across three browsers, signing in once for a whole suite, API checks alongside UI tests and a mobile viewport regression.