For the complete documentation index, see llms.txt. This page is also available as Markdown.

Coverage

See what your app does, how much of it your tests cover, and run coverage.

Coverage maps your application's user-facing areas (AI-derived from the connected source repo) to the UI tests that exercise them, and — when you collect it — to execution-line coverage from a build/test run. It answers "what does this app do, and what isn't tested yet?".

Coverage needs a connected source repository (Settings → Source Code). The AI area scan and the execution-coverage run both read through that connection. Authoring corrections (renaming areas, remapping files) stays in the app.

Operation
What it does

The coverage snapshot: rollup, areas, targets, and the latest scan status.

Start the AI area scan (enumerate source, derive areas).

Recent execution-coverage runs.

Start an execution-coverage run for a build/test target.

scan_coverage and run_coverage are long-running and fire-and-forget — they return immediately and you poll get_coverage (its scan.status / runActive) or list_coverage_runs. See Long-running operations.

Last updated

Was this helpful?