// practical playwright training

Write Playwright tests that hold up.

Practise on real-world challenges: pick resilient locators, wait without sleeps, mock the network, check accessibility. Your code runs in a real browser and a hidden validator checks what happened. Start right here: an AI suggested three locators for this page, and each one is wrong.

All 30 challenges are free. Challenges 1 to 10 work without an account; a free account (no card) opens 11 to 30.

JavaScript + PlaywrightNothing to installNo card needed

Locator warm-up: write a Playwright locator for the sample page

LOCATOR WARM-UP
  1. Round 1: current
  2. Round 2: to do
  3. Round 3: to do

Remove the keyboard from the basket

AI suggestedgetByRole('button', { name: 'Remove' })

Your basket

Mechanical keyboard£89.00
USB-C cable£9.00
Continue shopping

Run the AI's suggestion to see what's wrong with it, then write a better one.

30 challenges live4 learning tracksA fresh Chromium for every runBonus points for getByRole and friends

// how it works

Write it. Run it. Know why.

  1. Step 1: Take on a real scenario

    Each challenge is a real-world testing problem on a real practice page: delayed content, two tables with lookalike rows, a request to mock, a form to check for accessibility. Write the Playwright code in the browser editor. No setup, no imports.

    await page.getByRole('button', { name: 'Sign in' }).click();
  2. Step 2: Run it in a real browser

    Your code runs in a fresh Chromium and a hidden validator checks what actually happened on the page, not just whether your code ran. You get pass or fail, the logs and a video of the run.

  3. Step 3: Learn what holds up

    After your first pass, compare your code with the reference solution. Earn points, bonus points for resilient getBy… locators and a daily streak as you move through four tracks, from Foundations to Expert & Verification.

Start where you are.

COMING SOONFIRST CHALLENGE LIVE

Works on my machine

Tests that pass on your laptop and fail in CI. Practise finding the timing bug and fixing it, so the test passes on every run, not just yours.

Try the first one: Fix the Flaky Test

We'll only use your email to tell you when the Works on my machine track opens. See our Privacy Notice.

// if you test manually today

Start from the flow you already know.

You already know what to check. Learn to automate it one readable step at a time: open a page, click, fill a form, wait for results.

Try challenge 1, no sign-up

// if you’re new to automation

Fewer flaky tests start here.

Practise the habits that keep tests stable: locators by role and label, waiting without sleeps, scoping to the right row.

Start with Wait for Dynamic Content

// if you already automate

Sharpen your judgement.

Full journeys, network payloads, device emulation and accessibility assertions, ending with debugging a broken test and writing your own checks.

Start with Inspect Network Payload

// who builds it

Built by a working test engineer.

“The hardest part of automation is rarely the framework. It’s the small, repeated decisions: which locator to choose, why a test passes locally and fails in CI, when to wait and when to assert. Those skills come from practice, not documentation.”

Babatunde · Test automation engineer, ManchesterRead the full story

// works on my machine · coming soon

Be first into
the CI track.

Tests that pass on your laptop and fail in CI. Get one email when the next challenges in the track open.

We'll only use your email to tell you when the Works on my machine track opens. See our Privacy Notice.