The Playwright Test Suite Day

A test automation engineer spends a day turning the flows you choose into Playwright tests, written by hand or drafted with AI, and hands you a pull request of tests that passed three runs in a row.

Every release, someone clicks through the same flows by hand and hopes. An end-to-end suite would catch the break on Tuesday instead of a customer finding it on Friday.

Our engineer automates your highest-priority flows in your repository, ideally from your written specs. Tests use role, label and test-id selectors and create their own data, so they fail when the app breaks, not when the layout moves.

A test only goes in once it has passed three runs in a row. Anything flaky is left out and explained. You get a pull request to review, never a surprise merge.

What's included

  • One 8-hour shift of a named engineer in your repository
  • On the first day, a Playwright setup with config, a login step and a README
  • Tests for your priority flows with stable selectors and their own test data
  • Every test green three runs in a row before it is included
  • A CI job on GitHub Actions, GitLab CI, Bitbucket Pipelines or Azure Pipelines, where you already have CI
  • A pull request listing tests added, tests left out and why, and the next flows

How it works

  1. 01

    Book and send access

    Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.

  2. 02

    We do the work

    An experienced employee who specialises in this task works through it, and asks before anything outside the scope.

  3. 03

    Delivered with evidence

    You get everything listed on this page, with a written account of what was done.

Before you order

Have these ready so we can start the moment you order. The delivery clock only runs while we have them.

Who it's for

Web app teams who want regression testing that runs itself on every change.

Questions

Do you need our specs?

They help a lot. With written specs we automate exactly what you defined. Without them we agree the flows at the start of the day.

Does it run in our CI?

Yes, if you have CI. We add a job to your existing pipeline. To set up CI from scratch, book The CI Runner & Pipeline Setup.

Will you change our application code?

No. Where an element has no stable selector, we list it in the pull request as needing a data-testid. A Developer Day can add them.

What about flaky tests?

We only include tests that pass three runs in a row. A test that does not is left out and the reason recorded.

Often booked alongside