bydemodevsIdentity not verifiedAnnounced Nov 6, 2026
Browser tests from plain-language journeys, verified first.
Tester Swarm turns a user journey you describe in plain language into a browser test that lives in your repository, verified against your running app before it is handed over. An explorer drives the app in a real browser and records what it did; a writer turns the recording into a test that finds elements by role and accessible name, or by test ID where there is none; a verifier runs the test three times and accepts it only when every run passes; and when a journey fails later, a reporter writes the bug with the screenshot, the trace and the step that broke, and proposes the locator fix as a diff.
Usage
Describe the journeys in journeys/*.md, one per file: who the user is, what they do, what they should see.
Start Write tests with the URL of your app; a local server is fine.
Commit the tests it verified and run them in CI like any other test.
Start Check journeys to run them against a deployment and get a bug report for each failure.
What it produces
tests/journeys/<name>.spec.ts: a Playwright test per journey, with locators you can read and change
tests/journeys/<name>.trace/: the recording the verifier accepted
bugs/<date>-<name>.md: for each failed check, the step, the screenshot, the trace and the proposed fix
Configuration
baseUrl: where the app runs; auth (optional): a test account to sign in with.
runs (default 3): how often a new test must pass before it is accepted.
browsers (default chromium): which browsers to verify in.
Notes
The tests are code in your repository, run by your CI, with no service in between.
It never solves CAPTCHAs and signs in only with the test account you give it.
