OpenParable
Skip to content
← Back to skills

Running Coverage

Testing & Quality
running-coverage

Running Coverage is an Agent Skill for testing & quality published in the intentee/paddler repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Runs every test suite in the paddler workspace on the fastest available device, and produces code coverage report. Use when the user asks to run the code coverage, or to check the coverage.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/intentee/paddler/blob/HEAD/.claude/skills/running-coverage/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/running-coverage, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Running the code coverage

Run every test suite in the workspace, picking the fastest compiled device backend for the host, then report the workspace code coverage.

Step 1: detect the device

Run this once at the start and echo the chosen device:

if [[ "$OSTYPE" == "darwin"* ]]; then
  DEVICE=metal
elif command -v nvidia-smi >/dev/null 2>&1 && nvidia-smi >/dev/null 2>&1; then
  DEVICE=cuda
else
  DEVICE=cpu
fi
echo "Device: $DEVICE"

$DEVICE selects the Rust integration suite variant in Step 2. The other four suites don't take a device feature.

Step 2: run the code coverage

Copy this checklist and tick each item as the suite completes:

TEST_DEVICE=$DEVICE make test.coverage

Step 3: rules during the run

  • Serialize GPU suites. When $DEVICE is cuda or metal, run test suites sequentially to avoid device contention.
  • Per-test 30 s budget. Flag any individual test that exceeds 30 s wall-clock. That is a real bug — production or test — not flakiness.

Step 4: report

After the coverage suite finishes, sum up the results in an actionable report.