What problem does it solve?
Identifies whether a dashboard "dive" is safe to ship by validating that the UI renders correctly, rendered values match seed and warehouse data, interactive controls work, methodology/verify modals are present and accurate, edge cases are handled, and performance/network behavior is within budget.
Core Features & Use Cases
- Dual-phase render validation: verifies Postgres-proxy first paint and WASM upgrade behavior with screenshots and snapshots.
- Data correctness checks: compares rendered UI values to verifications seeds and live warehouse queries to detect stale or miswired data.
- Interactivity and contract checks: exercises manifest-declared controls via headless browse to confirm click mutations and URL presets work, and validates Methodology and Verify modals.
- Edge-case and performance audits: scans for formatting/null bugs, nonsensical ratios, console/network errors, and request storms, and produces a gate-by-gate artifact report.
- Use Case: run before promoting a dive to catch customer-visible defects like decimal-place or aggregation bugs that would mislead users.
Quick Start
Run a complete dashboard review for the dive id <dive-id> against the base URL <base-url> and produce the artifacts report.