Live demo — no signup

The dashboard your team gets on day one.

This is the real thing, filled with sample data. Every run, every bug and the QA-health metrics that tell you whether you can ship — pass rate, flakiness, defect escape rate, MTTR, coverage and DORA. Sign up and it’s seeded with your own demo workspace in seconds.

qaspider.app / dashboard

Projects

Runs (recent)

Open bugs

QA health

7-day rolling · demo data

Pass rate

On target

96.4%

Target >95%

Green CI runs over the last 7 days. Below 90% and developers start ignoring the pipeline.

Flakiness rate

Watch

2.8%

Target <2%

Drifting up. Quarantine the top 3 flaky tests this week before trust erodes.

Defect escape rate

On target

4.1%

Target <5%

Bugs reaching production vs. caught pre-release — the metric that maps to real user pain.

Critical-path coverage

Watch

88%

Target >90%

Two P0 flows (checkout, password reset) still lack end-to-end cover. Close the gap next sprint.

MTTR · P1

On target

19h

Target <24h

Median time to resolve a P1 defect. High MTTR usually means a process bottleneck, not a hard bug.

Suite duration

On target

12.4min

Target <15 min

Full pipeline wall-clock. Creeping up — profile the slowest 10% of tests before it breaks the loop.

Open bugs by severity

11 open

Delivery · DORA

Deployment frequency
top: multiple / day
4.2 / day
Lead time for changes
top: < 1 day
18 h
Change failure rate
top: ~5%
6.8%
Failed-deploy recovery
top: < 1 h
42 min

Recent runs

Project	Env	Status	Passed	Failed	Flaky
catapult	dev	passed	48	0	0
porsche	staging	failed	71	3	0
google	prod	flaky	12	0	2
catapult	dev	passed	47	0	1

The other half — QA Copilot

Not just a dashboard — a QA copilot.

Describe what you want tested and the Helper drafts a review-ready artifact — a test plan, test cases, a test story, a bug verification and more. Here’s one it produced:

Test planTest casesTest storyVerify bugSmoke storyBug reportRegression checklistEdge cases

Verify bug — Dealer discount badge times out at checkout

How to reproduce the reported bug, confirm the fix once it ships, and guard against it coming back. Ties to the tracker item so the fix and its test travel together.

Reproduction

P1Reproduce on staging
1. Sign in with a seeded dealer account
2. Add an eligible item to the cart
3. Apply a valid dealer discount code at checkout
Expected — BUG: the request hangs and the discount badge never renders (currently reproduces).

Verification after fix

P1Badge renders within SLA
1. Repeat the reproduction steps on the fixed build
Expected — The discount badge renders in under 2s and the total reflects the discount.
P2Failure is graceful
1. Force the discount service to error (feature flag or mocked 500)
Expected — A clear inline error is shown; no infinite spinner, no double-submit.

Regression guard

Add a contract test on the discount endpoint asserting p95 latency and a 200 with the badge payload.
Add the fixed flow to the checkout regression suite so it runs on every deploy.

Reproduction and fix-verification mutate cart state — dev/staging only, never prod.
Link this verification to the tracker item so the fix and its test stay together.

Open the Helper →Try all 8 skills — no signup

Make it yours.

Create a workspace, invite your team, and point the spider at your product. You’ll start on this exact view with demo data, then swap in your real projects.

Get started free