Test automation

Playwright test automation

A suite over the flows that cost you money when they break, running on every push. Available on applications we did not build, which is most of this work.

What you get

The flows that matter, not a coverage number

Login, checkout, booking, permissions. Named in the language your business already uses, so a red build says what broke and who it affects rather than which file threw.

Three engines

Chromium, Firefox and WebKit. The bugs that only show up in Safari are real, and this is usually how they get found before a customer finds them.

Wired into your pipeline

Runs on every push, in whatever you already use - GitHub Actions, Jenkins, something else. Not a suite somebody has to remember to run.

Written to be owned by your team

Readable and extendable, handed over with documentation. A clean handover is a supported ending rather than a lost retainer.

What this does not cover

  • Migrating an existing suite from another framework, and cleaning up somebody else's flaky tests - both tend to become open-ended commitments and are not taken on
  • Load and performance testing, which is a different discipline with different tools
  • Manual QA

Questions

Can you test an application you did not build?
Yes, and it is the more common engagement. Writing tests does not require having written the application - often the opposite helps, because a fresh reader finds the assumptions the original team stopped being able to see.
Will you work in our repository?
Yes. Your repo, your branch strategy, your review process. The suite arrives as pull requests like any other work.
What does $2,500 buy?
A starting suite over the handful of flows that would hurt most, wired into CI and actually running. It is a starting point rather than a menu price: the number depends on how many flows matter and how much work it takes to get the application into a testable state.

Find out what breaks before your customers do.

Tell us which flows would cost you most if they stopped working tomorrow. That is usually the entire scoping conversation.

Start a project →