TAMASH · RunSightsEvery Playwright and Cucumber run, from laptops and CI, as it happens. RunSights shows what newly failed, what got fixed, what is flaky, and the likely cause of each failure.
Included with Shield and Forge. Also on its own.
The local report tells one person how one run went. RunSights tells the team what every run means.
Runs appear while they are still going. Shards of one CI build merge into one run. Filter by branch, environment, cycle or release.
The same failure across tests and runs is one group, with a likely cause and the evidence. Review it once.
Any run against the one before it: what a change fixed, broke or healed.
A signed-in machine sends its runs under the person's name. An organization can collect CI runs only.
A service token for the pipeline. Traces, videos, screenshots and the Playwright HTML report are uploaded with the run and kept for 14 days.
Runs of tests linked to Forge test cases count toward their cycles.
One line in the reporter list of playwright.config.ts. The local dashboard still writes next to your project for the person who ran it.
A formatter beside your console formatter. Each scenario is a test, each example row its own test, and the Playwright calls of each step are listed.
GitHub Actions, GitLab CI, Azure Pipelines, Jenkins, CircleCI, Buildkite and Bitbucket are recognised from their variables: the run links back to the job that made it.