Test Progress
Testing & Qualitytest-progressTest Progress is an Agent Skill for testing & quality published in the linq2db/linq2db repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Report the live test-progress heartbeat for linq2db test runs (read-only). The heartbeat is written by runs launched per this instruction set (test-runner passes --test-progress), so this skill reads the latest .build/.agents/test-progress.*.json and relays a one-line status — current test, completed/total, pass/fail tally. Use when the user says "/test-progress", "how far along are the tests", "watch the test run", "test status".
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/linq2db/linq2db/blob/HEAD/.agents/skills/test-progress/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/test-progress, 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.
/test-progress
Report the live progress heartbeat written by the test assembly during a run. Backed by Tests/Base/TestProgressReporter.cs; reader docs in .agents/docs/testing.md → Monitoring a long run.
When to run
Invoke /test-progress to check on an in-flight or most-recent test run — "how far along are the tests", "test status", "watch the run". Use /test to write or start tests, and /test-providers for provider / container setup; this skill only reads the heartbeat and never launches or edits anything.
How it works
The heartbeat is opt-in via the --test-progress command-line option on the test executable. Runs launched per this instruction set always pass it — test-runner appends --test-progress, and /test step 3.1a relies on that for long runs — so a heartbeat file is normally present for the active or most-recent run. There is no env var and nothing to toggle; this skill only reads the heartbeat.
The file lands at .build/.agents/test-progress.<tfm>.<pid>.json (one per TFM / process). For a run the user starts in their own terminal, they pass --test-progress themselves (see testing.md).
Steps (default / status)
-
Run the summary helper for the most recent run:
pwsh -NoProfile -File .agents/scripts/test-status.ps1Relay its one-line output (state, completed/total, pass/fail/skip, rate, elapsed, ETA, current test). If it reports no heartbeat file, say so — either no run has started, or the run was launched without
--test-progress(unusual for a Claude-launched run). -
Add
-Rawif the user wants the full JSON, or-Path <file>to target a specific run's heartbeat. -
For a parallel per-provider run, each process writes its own
.build/.agents/test-progress.<tfm>.<pid>.json; point-Pathat the one you want to watch.
Don'ts
- Don't toggle env vars or edit
settings.local.json— the heartbeat is controlled by the--test-progressoption, whichtest-runneralways passes. There is no on/off switch to flip. - Don't edit
Tests/Base/TestProgressReporter.csor any test source from here — this skill only reads the heartbeat. - Don't launch test runs from here — that's
/test. This skill reports the status of a run already in progress or finished.