Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

2.1 KB
Raw Blame

Screenpipe Coverage

Screenpipe tracks coverage at two complementary layers:

  • Tauri/WebDriver E2E coverage: real product UX and local API behavior by platform.
  • Core engine coverage: Rust behavioral flow coverage across capture, audio, DB, accessibility, and engine crates.

These dashboards are behavioral maps, not a replacement for line or branch coverage. Use them to see which product risks are represented, then layer runtime job results and cargo llvm-cov data on top when judging release confidence.

Dashboards

Current Snapshot

Tauri E2E

  • Mapped specs: 144
  • Declared test blocks: 415
  • Weighted coverage points: 335.0
Platform Specs Declared tests Weighted points Layers Features Critical score
windows 110 352 294.6 15 125 85%
macos 140 377 304.8 17 134 88%
linux 98 310 264.0 14 122 80%

Core Engine

  • Mapped suites: 37
  • Mapped Rust files: 409
  • Active test blocks: 3974
  • Ignored/manual test blocks: 189
  • Weighted coverage points: 3275.3
Platform Suites Active tests Ignored tests Weighted points Layers Flows Critical score
windows 33 3811 171 3202.3 21 11 100%
macos 32 3854 150 3197.6 22 11 100%
linux 29 3389 146 2820.6 20 11 100%

Refresh

From apps/screenpipe-app-tauri:

bun run coverage:all
bun run coverage:all:check

For core line coverage, install/use cargo llvm-cov and feed its JSON summary into coverage:core; the core dashboard documents the exact command.