Faultsense Review 2026: The expect() Without the Page

Most end-to-end tests only ever run in CI, against seeded fixtures and a simulated browser. Faultsense flips that model: it runs your assertions against real user sessions, in the user’s real browser, on the real DOM they actually produced. The pitch is “the expect() without the page” — and the assertions live right next to the markup they check.

What is Faultsense?

Faultsense is a lightweight, zero-dependency browser agent for end-to-end assertions in production. Instead of writing assertions in a separate test script, you annotate UI elements with fs-* attributes: fs-assert for a stable key, fs-trigger for when it activates (click, change, submit, mount), and fs-assert-added / removed / updated / visible / hidden for the expected outcome.

The agent decides pass or fail in a real browser on the user’s own device. Because the assertion lives next to the markup, there’s no second codebase testing the first one — and no fixture that silently drifts from production.

Key features

• Attribute-based in-DOM assertions — fs-* attributes sit on the element they check and run wherever your app runs.
• Real-user-session testing (RUM-style) — every real session becomes a live assertion run, catching breakage that only appears under real network, data, and browser conditions.
• Dual-driver ready — the same assertions work for an AI coding agent in staging and real users in production, with no driver lock-in.
• Bring-your-own-sink — route pass/fail events to Datadog, your warehouse, an internal endpoint, or three sinks at once via the collectorURL option. No mandated backend.
• Conditional assertions & inline modifiers — handle multiple outcomes from one action; assert on text/regex, value, checked/disabled/focused state, element count, and CustomEvent detail fields, all inline.
• JSON-spec instrumentation — for third-party widgets or generated markup you don’t control, declare the same assertions as a JSON spec.
• Framework-agnostic — verified conformance matrix covers React 19, Vue 3, Svelte 5, Solid, Alpine, Astro 6, Hotwire, HTMX, Livewire, and Phoenix LiveView.
• Near-zero overhead — 17.7 KB gzipped, zero dependencies, 0 ms INP impact measured at 1000 assertions under 4× CPU throttle.

Who should use it?

Faultsense is built for teams who want production-grade confidence in their critical flows — checkout, signup, payment confirmation — without trusting CI fixtures alone. An e-commerce team can annotate the Place Order button and get a failed event sent to their warehouse the moment a release breaks the confirmation for a specific cohort.

It also fits AI coding-agent workflows: point an agent at staging flows and let Faultsense surface breaks before you ship, then keep the same assertions running in production.

It’s a harder sell if you just want a conventional Playwright suite and don’t want to rethink where assertions live. And because it’s early-stage, the Shadow DOM gap (Lit, Stencil, Salesforce LWC) and the need to trust in-production assertions are real considerations.

How it compares

Traditional E2E tools like Playwright and Cypress live in CI and assert against fixtures. Faultsense lifts the assertion half onto the DOM and runs it in the field. Sentry or Datadog RUM tell you something broke; Faultsense lets you declare what “right” looks like and fails loudly when a real session violates it. They compose — Faultsense events can stream straight into Datadog, and you can keep your existing Claude Code or Cursor workflow intact.

Pros and cons

Pros: novel, correct mental model; outstanding performance discipline (17.7 KB, zero INP impact at 1000 assertions); framework-agnostic with a verified conformance matrix; bring-your-own-sink; thorough documentation.

Cons: very early (4 stars, 8 commits); FSL-1.1-ALv2 is source-available but not OSI open source; managed-sink pricing unpublished; Shadow DOM unsupported; no first-party dashboard — you depend on your own sink.

Pricing

Free and source-available under FSL-1.1-ALv2. Route events to your own warehouse, Datadog, or internal endpoint at $0. A managed collector is hinted at but not yet priced.

FAQ

Does Faultsense replace Playwright or Cypress? No. It complements them — the README frames it as “the expect() without the page.” Keep your CI suite; add Faultsense for in-production verification.

What frameworks are supported? Any that render HTML: React 19, Vue 3, Svelte 5, Solid, Alpine, Astro 6, Hotwire, HTMX, Livewire, and Phoenix LiveView, all verified in the conformance suite.

Is it really zero-dependency? Yes — the npm package is 17.7 KB gzipped with no runtime dependencies, and the default entry is SSR-safe (touches no window/document on import).

Does it hurt my Core Web Vitals? In stress tests, 0 ms INP impact even at 1000 assertions, zero new long tasks in steady state. See the ai-code category for more performance-focused tools.