Existing Playwright suites
Already have a Playwright suite? Run it through verifAIed and each of its tests is tracked on your branch, with no re-recording.
Track your suite
Put verifAIed in front of the command that runs your suite:
verifaied collect -- npx playwright test
Your suite runs as it always does, and the command exits with the suite's own exit code. Each test() in the run becomes one suite test on the branch, and its pass or fail lands there like a recorded test's does.
The same run also measures the code your suite reached in the browser, once your app is set up for it. See Code reached.
Add the json reporter
verifAIed reads Playwright's json report, so your Playwright config must list that reporter. Add this to its reporter list, beside the reporters you already use:
["json", { outputFile: "playwright-report/report.json" }]Without it, the run says so and tracks nothing.
Suite tests on the Browser Tests page
- A suite test's row carries a
suitechip. - Suite tests are grouped by the path of their own test file.
- When a later run of a test file no longer contains a test, the test is kept and marked not seen in latest run. It may have been renamed, skipped or removed, and only you know which. Delete it on the web if it is gone for good.
What a suite test cannot do
verifAIed only reads a suite test. Your own runner is the only thing that runs it. So a suite test cannot be:
- recorded again or edited in the studio,
- run from the web or with
verifaied test run, - used as a pre-step,
- inserted into another test.
To update its result, run your suite through verifaied collect again. A suite test also takes its address from your own Playwright config, not from the environments in .verifaied/config.toml.
Suite tests and done
A suite test counts for done the same way a recorded test does. See Definition of done.