ai.turnsignal/turnsignal

Read-only Playwright CI results for coding agents: tells whether a failing test is new in this PR, already failing on main, or known flaky, with per-test history.

turnsignal.ai पर देखें

दस्तावेज़

The merge-or-fix verdict for every Playwright PR.

TurnSignal tells you which failures your change caused, which were already failing on main or are just flaky, and which tests your crashed shards silently dropped.

What is TurnSignal? · Free during the beta · No credit card · No repository access · Limits · Security

By signing in you agree to the beta terms and the privacy notice.

Example run · checkout-web · main ← feature/saved-cards

812 passed 4 flaky 2 failed 3 missing 14 skipped

New failure checkout › pays with a saved card

tests/checkout/payment.spec.ts:42 · chromium

Passed on the latest main run, fails here.

Missing search › filters by price

tests/search/filters.spec.ts:18 · chromium

Started on worker 3 but never finished: the runner died mid-test (crash or out-of-memory kill).

Known flaky profile › uploads an avatar

tests/profile/avatar.spec.ts:9 · firefox

Failed on attempt 1 (Timeout 5000ms exceeded), passed on attempt 2.

Built for the questions you ask after every run

Did my change break this? Is it just flaky? Did we lose any results?

A verdict on every run and PR

Each run opens with one plain sentence: what failed, why it matters and what to do. On GitHub, the same verdict is posted as a sticky PR comment.

No test goes missing

Results are written to disk in CI before they are sent. If a runner crashes or is killed, every test it never finished is listed as Missing, with the likely reason and the lowest free memory on that machine.

New, already broken or known flaky

Every failure is compared with the default branch, so you can tell a failure your change caused from one that was already there.

Flaky tests with evidence

See which tests were flaky in the last 7 to 90 days, how often, and the exact runs and attempts behind each label.

Never breaks your CI

The reporter fails open: if our API is down, your tests run as usual and the exit code is untouched. Results stay on disk, and npx turnsignal upload sends them afterwards.

Secrets stay in your CI

Common secret formats (tokens, passwords, keys) in errors and traces are redacted before anything leaves your CI, and errors are checked again on our servers. Screenshots and videos can't be redacted, so you choose whether to send them.

Also included: the Playwright trace viewer, videos and screenshots in the browser, report-only quarantine with an owner and an expiry, turnsignal governance to review what AI agents changed in your tests, Slack and Discord alerts, and an MCP server for your coding agent. Read the docs

First run in a few minutes

Add one reporter line. Your existing reporters keep working.

  1. Install the reporter

    npm i -D turnsignal
    Copy

  2. Add it to playwright.config.ts

    reporter: [['list'], ['turnsignal']],
    Copy

  3. Add one secret in CI

    Sign in, create a project and copy its token from the setup page. 
    TURNSIGNAL_TOKEN=<your project token>
    Copy

Free during the public beta

TurnSignal is in public beta: every feature is free while we work with the first teams. No credit card.

  • Each organization can record up to 3,000 runs and 300,000 test results a month, in up to 5 projects. Need more? email hello@turnsignal.ai and we'll raise it.
  • Organization owners are warned at 80% and 100% of the limit: in the dashboard, and by email when we have their address. Over the limit, runs that already started still finish; new runs aren't recorded until the 1st of the next month (UTC), and your CI passes or fails exactly as it would without TurnSignal.
  • Paid plans will come later. We'll announce them at least 30 days before anything changes. There's no card on file, so nothing can be charged automatically: you decide whether to move to a paid plan.
  • The plans we intend to launch, and the founding-team offer (12 months free, then half price for life), are on the pricing page. Open-source projects stay free.
  • Beta means some things will change as we learn from you. See the beta terms.

Try it on your next run

Guides for Playwright teams

Practical answers to the questions that come up after a red run. More on the TurnSignal blog.