test-execution-tracker

name	test-execution-tracker
description	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.
license	MIT
metadata	{"author":"TheTestingAcademy","stlc-phase":"Test Execution","version":"1.0.0"}

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. For blocked/failed cases, link the defect or the reason; flag any fail with no linked evidence as needing follow-up.