Starting from zero: how long a Playwright E2E suite takes

What a Test Architect Setup includes, how long it takes, and why Audit Flash is the wrong entry point when you have no suite yet.

With no E2E suite, an audit has nothing to read. The right entry point is a base: pages, fixtures, a few critical flows, and a CI job that runs on your GitHub.

This is not “the whole application covered in a week”. It is a base your team can grow without me.

What you receive

a Playwright TypeScript repo, with a POM and test.extend()
the critical flows agreed on the scoping call, not a recording of every click
@smoke and @regression tags
a CI workflow (GitHub Actions, GitLab, Jenkins, CircleCI, or Azure DevOps)
a README for running the suite, and the coverage gaps written down as they are

The code is on your repository, under your licence. It runs without Doctests installed.

A public demo exists, on Sauce Demo: about 30 seconds of generation, 8 scenarios, coverage stated at 60%. The figures are on /services/preuve-generation. This is not a paying client.

How long, and at what price

2 to 3 weeks. €4,500 to €9,000. VAT is not charged.

The low end covers an application with a clear flow and little authentication state. The high end covers several roles, a checkout, or auth that needs scoping. The price is fixed after the call, not in a form.

The Calendly call is there to scope that quote. It is not there to sell an Audit Flash to a team that has no suite.

What I do not promise

100% coverage
a suite that will never move when the product moves
a subscription so you can keep running the tests

After delivery, you can continue with a retainer (€1,200–2,000 / month) if you want a safety net. That is not included in Setup.

If you already have Playwright

Do not buy a Setup to “redo everything”. Start with an Audit Flash: €490, a plan of what is breaking, then a sprint only on the tests that block CI.