Playwright or Smoketest?
Choose Playwright when your engineers want to write and own their test code. Choose Smoketest when you want each ticket tested as it reaches QA, with no test code to write, from $399 a month.
1import { expect, test } from "@playwright/test";2import { pdfText } from "./helpers/pdf";34test("invoice PDF", async ({ page }) => {5 await page.goto("/billing");6 await page.getByText("Add seat").click();7 const total = page.getByTestId("total");8 await expect(total).toHaveText("$312.40");9 const file = page.waitForEvent("download");10 await page.getByText("Download PDF").click();11 const pdf = await pdfText(await file);12 expect(pdf).toContain("Proration");13 expect(pdf).toContain("$312.40");14});With Playwright, your team writes the tests.With Smoketest, each ticket comes back tested.
Here is one ticket,handled both ways.
Playwright gives your engineers exact control, which is why so many teams use it. The difference is who does the work.
Show proration on the invoice PDF
When an Admin adds a seat mid-cycle, the invoice PDF should carry the proration line and match the invoice preview.
1 failed. invoice-pdf.spec.ts
Expected $312.40, received $294.00. The trace is in the run's artifacts.
trace.zip
Failed · 1 of 4 requirements not met · 2m 38s · Attempt 1
The invoice PDF leaves out the proration line. The preview says $312.40 and the PDF says $294.00.
Next: moved to In Progress. Move the ticket back into QA to test again.
Watch the recording · View attempt
The same eight questions, asked of both.
Some teams should stay with Playwright.
Here is how we would decide if we were in your seat. On a call we will tell you which side you are on.
Choose Playwright when
- Your engineers want to write and own their tests
- A few flows need the same exact check on every build
- You have people with time to look after the suite
Choose Smoketest when
- Nobody has time to write or look after tests
- You want every ticket tested the moment it reaches QA
- You want to start this week, from $399 a month
You can run both.
Keep your Playwright tests for the flows that must never change. Smoketest takes the new work on each ticket, where nobody has written a test yet.
Our founder sets it up with you on a real ticket.
A call with our founder
Tell us how your team ships and where tickets wait. We will tell you whether it fits.
A real ticket, same day
We set it up with you on your own board, so it can start the day of the call.
A plan shaped to you
It starts from $399 a month. Scale is designed with teams that need more runs.
It changes as you do
New flows, new tools, a new QA hire. We keep adjusting it with you as you grow.
Questions about Playwright
Laying out every option? See them side by side
Playwright is free and open source. The cost is your team's time to write the tests, run them, and look after them as the product changes.
It starts at $399 a month for 1,000 runs. Each run is up to 10 minutes, and a longer test counts as two runs or more, one for every 10 minutes. If your team needs more, we design a Scale plan with you, so you stop buying extra runs.
No. Keep them. Smoketest starts from your tickets, so it does not need your tests, and the two run side by side.
No. Write the ticket the way you do today. It works out what to test from the ticket, the pull request, and your playbook.
Yes. A deployment or a pull request check can start a test, as well as a ticket reaching QA.
Besides web apps, it tests mobile apps on iOS simulators and Android emulators, APIs from your OpenAPI spec, MCP servers, and AI agents.
Every result links to the recording, the steps, and the reasoning, and says what it did not test, so you can check its work the way you would check a teammate's.
A named person on your team. Smoketest gives them the evidence: what passed, what failed, the recording, and what it did not test. It never signs off a release.
Give it a ticket nobody has written a test for.
Book a call and we will test it with you. You get the result and the recording the same day.