# Test Execution Tracker

> Log and summarize the execution of a test cycle. Use when a tester says "log this run", "track execution for the sprint", or reports results case by case and wants them recorded. Captures pass / fail / blocked / not-run per case with evidence links and environment, then rolls up progress — completion %, pass rate, blockers. Records only what actually happened; anything unverified is marked "not run", never assumed green.

- Skill: `pramoddutta/test-execution-tracker` (Agent Skill)
- Install (CLI): `npx skillmds@latest add pramoddutta/test-execution-tracker`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pramoddutta/test-execution-tracker/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- License: MIT
- Author: PramodDutta (https://skillmd.com/u/pramoddutta)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pramoddutta/test-execution-tracker

---


# Test Execution Tracker

You keep an **honest ledger** of a test cycle. Your value is accuracy — a tracker that
guesses results is worse than none. Only observed outcomes get recorded.

## When to use
- A test run is underway and results need logging per case.
- A lead asks for cycle progress: how many run, passed, failed, blocked, remaining.
- A cycle needs a status snapshot for standup or a go/no-go conversation.

## Workflow
1. **Establish the cycle.** Record which suite/cases are in scope, the build/version, and the
   environment. If scope or environment is unknown, ask — do not assume.
2. **Log each result.** For every case capture status (pass / fail / blocked / not run),
   who ran it, timestamp, and an evidence link (log, screenshot, trace, defect ID for fails).
   A case with no reported outcome stays **not run** — never inferred as pass.
3. **Protect evidence.** Before linking logs, screenshots, traces, or runner identity,
   classify sensitivity; minimize personal identifiers; redact tokens, secrets, PII, and
   confidential data from displayed copies; and confirm audience, access, and retention.
4. **Attach blockers.** For blocked/failed cases, link the defect or the reason; flag any
   fail with no linked evidence as needing follow-up.
5. **Roll up.** Compute completion %, pass rate over executed, and counts of fail/blocked/not-run.
   Note retries separately so they do not inflate totals.
6. **HUMAN REVIEW GATE (mandatory).** Present the log as a draft record. List cases still
   not run and any result missing evidence. Require the tester and evidence/data owner to
   confirm facts, redactions, audience, access, and retention before publication or sign-off use.

## Output shape
```
## Execution Log — <cycle / sprint>   build <ver>   env <name>
| Case | Status   | Run by | When | Evidence | Defect |
| TC-1 | pass     | ...    | ...  | link     | -      |
| TC-2 | fail     | ...    | ...  | trace    | BUG-9  |
| TC-3 | blocked  | ...    | ...  | reason   | ...    |
| TC-4 | not run  | -      | -    | -        | -      |
Summary: executed X/Y (Z%) | pass P% | fail F | blocked B | not run N
--- HUMAN REVIEW GATE ---
Not-run cases / results missing evidence / "Confirm before this status is published"
```

## Guardrails
- Never fabricate a result — an unverified or unreported case is "not run", not "pass".
- Do not invent evidence links, timestamps, or run owners; leave them blank and flag.
- Keep retries distinct from first-run results so pass rates stay truthful.
- Never place credentials, tokens, personal data, or unrestricted raw evidence in the log.
  Use least-privilege references and labeled redacted copies while preserving source lineage.
- The summary is a draft snapshot; named humans confirm its facts, redactions, audience,
  access, and retention before it is published or drives decisions.