Runs
Playwright CI debugger
Go from failed CI run to likely cause, evidence, and next step faster.
my-app
public-my-app
failed
production
my-app local run
Permanent demo for Sentinel, a Playwright CI debugger. Open one failed run and see grouped root causes, likely cause, strongest evidence, and the next debugging step. This link does not expire.
Run summary
Core context for this workflow.
Branch
main
Commit
8b98c45
Triggered by
Adnan
Environment
production
Run insights
Primary failure pattern and impact.
Primary failure
Assertion mismatch
getByTestId('metric-pass-rate') showed "88%" instead of "89%" before the 5000ms timeout.
Locator: getByTestId('metric-pass-rate')
4 tests impacted
Recurring failure detected
4 recurring
This analysis was generated automatically from a failing Playwright CI run.
Get grouped root causes, likely cause, traces, logs, screenshots, and video for your own tests
Sentinel is built to reduce time to debug Playwright CI failures, not just generate another report.
Setup in ~60 secondsSecrets automatically maskedWorks with Playwright CI
Views
92
Total jobs
1
Failed jobs
1
Failed tests
4
Total duration
9s
Started
Mar 21, 2026, 10:29 AM
Finished
Mar 21, 2026, 10:30 AM
Longest test
app.spec.ts > Sentinel demo E2E > run health + AI insights render (6s)
Failure trend
-
Failed tests
4 failing tests in this run.
Shared root cause detected
AI
UI assertion mismatch
4 failures in app.spec.ts share the same failure family.
Affected tests: 4Category: ui_assertion_mismatch
Sentinel detected a shared root cause across 4 failing tests. Fixing this issue will likely resolve multiple failures.
Cluster debug
Method: fuzzy
Strong shared signals: 4
Average similarity: 80%
Why these tests were grouped
- • Same failure family: UI assertion mismatch
- • Same file: app.spec.ts
UI assertion mismatch
4 failures in app.spec.ts share the same failure family.
4 tests
app.spec.ts·6s·chromium
getByTestId('metric-pass-rate') showed "88%" instead of "89%" before the 5000ms timeout.
Root cause: UI assertion mismatch
Grouped because: failure family UI assertion mismatch • file app.spec.ts • 80% match
app.spec.ts·5s·chromium
getByTestId('gate-mobile-feature-flags') showed "Locked" instead of "Open" before the 5000ms timeout.
Root cause: UI assertion mismatch
Grouped because: failure family UI assertion mismatch • file app.spec.ts • 80% match
app.spec.ts·5s·chromium
getByTestId('dataset-payments-uat') showed "Resetting" instead of "Available" before the 5000ms timeout.
Root cause: UI assertion mismatch
Grouped because: failure family UI assertion mismatch • file app.spec.ts • 80% match
app.spec.ts·5s·chromium
getByTestId('webhook-status') showed "Healthy" instead of "Degraded" before the 5000ms timeout.
Root cause: UI assertion mismatch
Grouped because: failure family UI assertion mismatch • file app.spec.ts • 80% match
Start debugging Playwright CI failures faster
Turn your next failed run into a debugging page with grouped root causes, likely cause, strongest evidence, and a clear next step.
Likely cause + next stepGrouped root causes across shardsTrace, logs, screenshots, and video
Setup in ~60 secondsSecrets automatically maskedWorks with Playwright CI