Expand description
Supercov’s single coverage engine. Target-language runtime adapters remain thin generated shims; instrumentation, orchestration, analysis and queries are owned here.
Modules§
- agent_
json - assertion_
coverage - Assertions coverage: which executed statements a test would catch breaking.
- child_
signal_ guard - Take the test processes down with the runner.
- coverage_
analysis - Language-neutral coverage arithmetic and masking MC/DC witness search.
- coverage_
export - LCOV and Cobertura exports, written from the shared run view.
- coverage_
html - A static HTML report: one file, no network, no service.
- coverage_
index - Typed coverage columns stored in the immutable query-index container.
- coverage_
query - Language-neutral coverage query operators.
- coverage_
report - Language-neutral reconstruction of coverage views from frozen obligations and per-attempt evidence.
- docker_
servers - A server a browser suite starts with
docker compose, built from the copy the suite runs in. The image holds the instrumented code, but nothing else crossed into the container: not the environment that tells the server’s runtime where to write, and not the directory it writes to. Adockerlauncher on the suite’s PATH hands each service built from the copy that environment and Supercov’s directory, mounted at the path it has outside, and records the project so the run can stop it, and read what it wrote, once the command ends. - evidence_
archive - Language-neutral, streaming implementation of the frozen evidence archive.
- frontend_
detection - Language/frontend selection for the zero-configuration public command.
- frontend_
protocol - Validation boundary between language-specific producers and shared Rust analysis.
- go_
instrumenter - Supercov-owned Go parsing and obligation discovery.
- go_
project - Go project discovery: what Supercov measures, and what it deliberately does not.
- go_run
- Public, isolated Go coverage run lifecycle.
- go_
test_ harness - Binding Go’s test functions to the evidence they produce.
- indexed_
query - One agent-query implementation over an authenticated immutable query index.
- integrity
- Language-neutral run integrity fingerprints.
- interned
- Ids a coverage report names over and over, stored once.
- javascript_
frontend - JavaScript source frontend for Rust-owned executions.
- javascript_
run - Rust-owned JavaScript execution for the public Supercov engine.
- js_
instrumenter - First oxc-backed vertical slice of the Rust JavaScript instrumenter.
- jvm_
instrumenter - Supercov-owned Java and Kotlin parsing and obligation discovery.
- jvm_
project - JVM project discovery for Maven and Gradle layouts.
- jvm_run
- Public, isolated JVM coverage run lifecycle, for Java and Kotlin.
- lifecycle
- Crash-safe run publication, recovery and explicit retention.
- orchestration
- Language-neutral execution plans over the Rust process supervisor.
- owned_
evidence - Turning what a Supercov-owned runtime wrote into the model the report reads.
- owned_
server - A server a browser suite drove, measured by a runtime Supercov owns: Go and the JVM. Their probes store into one array, which cannot tell two requests apart, so the runtime sweeps it on a clock into windows, and each window is credited, by time, to the one browser test whose span it overlaps. What no single test’s window holds is no test’s.
- patch_
view - Changed-line coverage: are the lines this change touches tested?
- probe_
v2 - process_
supervision - Privacy-preserving child-process supervision for arbitrary test commands.
- progress
- A single branded status line on stderr while a long, otherwise-silent step runs.
- project_
discovery - Runner/build/project discovery for zero-configuration JavaScript suites.
- python_
evidence - Validation and normalization of the Python runtime’s evidence records.
- python_
instrumenter - Supercov-owned Python obligation discovery.
- python_
project - Python project discovery and ahead-of-run obligation preparation.
- python_
run - Public Python coverage run lifecycle.
- query_
index - Immutable, versioned, fixed-layout query-index container.
- ruby_
evidence - Validation and normalization of the Ruby runtime’s evidence records.
- ruby_
instrumenter - Supercov-owned Ruby obligation discovery.
- ruby_
project - Ruby project discovery and ahead-of-run obligation preparation.
- ruby_
run - Public Ruby coverage run lifecycle.
- run_
currency - Whether a run is still a record of a checkout whose test-side files have moved on, judged file by file.
- run_
merge - Atomic, integrity-checked merging of independently executed run shards.
- run_
query - Agent-facing queries over persisted run metadata.
- run_
store - Validated local run discovery and immutable run identity.
- run_
view - One versioned view of a run, shared by every gate, export and report.
- rust_
build_ cache - Exact-input stable workspace metadata for the owned Rust frontend.
- rust_
cargo_ configuration - Exact pre-execution resolution for Cargo target runners.
- rust_
instrumenter - Supercov-owned Rust parsing and obligation discovery.
- rust_
owned_ doctests - Doctests for the owned Rust frontend, measured one doctest at a time.
- rust_
owned_ nextest cargo nextest runfor the owned Rust frontend.- rust_
probe_ transport - Bounded, lock-free, file-backed transport for owned Rust probe events.
- rust_
project - Cargo workspace discovery and isolated owned-Rust frontend preparation.
- rust_
run - Public, isolated Rust coverage run lifecycle.
- rust_
runner_ attempt - Exact attempt identity exposed by Rust test runners.
- rust_
runtime - Generated std-only runtime and strict reader for owned Rust probes.
- rust_
test_ context - Frozen Rust test-attempt context identity and supervisor collision preflight.
- rust_
test_ runner - Stable Cargo/libtest execution for the owned Rust frontend.
- security_
candidates - Syntax-level candidates for the security surface catalog, from oxc.
- served_
tests - The browser tests a measured server answered: what the browser runner reported for each attempt, which a Python or Ruby server’s run takes its tests from, and the rule that gives a request naming no test to one.
- source_
capture - What a run captures of its sources: each file’s text at the time of the run, fingerprinted into the manifest archived with the evidence, and the check that a later query reads the same bytes.
- source_
discovery - Deterministic first-party JavaScript/TypeScript source discovery.
- source_
manifest - What a run’s sources were: each captured file’s bytes and declarations,
the per-test execution record written when the run is published, and the
change model that says which tests a later edit could have reached.
tests affected,runs sourceand assertions coverage all read these. - source_
tools - Tools that judge the project’s source as text.
- source_
units - Declaration units and comment-blind digests of one source file.
- test_
kind - A Python or Ruby test’s kind from where it lives, read as the JavaScript
runtime reads one (
runtime/javascript/provenance.mjs): the nearest directory that names a kind, then the file’s own name, thenunit. A Rails app’s Capybara tests live intest/systemorspec/features, and its request specs inspec/requests; every one of them was reported as a unit test. - test_
loads - Which first-party files a JavaScript or TypeScript test file loads, read from its imports, and which test runner a configuration file belongs to.
- workspace
- Isolated project snapshots and crash-recoverable stable build cache.