AGENT SKILL

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.

License 许可
MIT
最近更新
2026-07-15
Stars
★ 4
Forks
8

01 前言 Front Matter

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

03 SKILL.md 正文

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. Attach blockers. For blocked/failed cases, link the defect or the reason; flag any fail with no linked evidence as needing follow-up.
  4. Roll up. Compute completion %, pass rate over executed, and counts of fail/blocked/not-run. Note retries separately so they do not inflate totals.
  5. HUMAN REVIEW GATE (mandatory). Present the log as a draft record. List cases still not run and any result missing evidence. Ask the tester to confirm before the summary is published or used for a sign-off decision.

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.
  • The summary is a draft snapshot; a human confirms it before it drives decisions.

04 同仓库更多 Skills

PramodDutta
PramodDutta/skillmasterclass

se-wait-fixer

Scans Selenium Java code for Thread.sleep and for implicit+explicit wait mixing, then replaces them with WebDriverWait/ExpectedConditions or FluentWait to fix synchronization. Use when an SDET says "remove Thread.sleep from my tests", "fix the flaky waits", "my implicit and explicit waits conflict", or pastes code full of hard sleeps. Produces refactors the engineer must run and confirm.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-test-generator

Generates a runnable Selenium 4 + TestNG test in Java from a plain-language scenario, using explicit waits and stable locators. Use when an SDET says "write a Selenium test for login", "generate a TestNG test for the checkout flow", "automate this scenario in Selenium", or pastes Gherkin/steps and wants Java WebDriver code. Produces a draft test the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-report-integrator

Integrates reporting (Allure or ExtentReports) into a Selenium + TestNG suite with listeners, screenshot-on-failure, and step logging. Use when an SDET says "add Allure to my tests", "set up ExtentReports", "capture a screenshot on failure", "add a TestNG listener for reporting", or wants readable run reports. Produces listener and config code the engineer must run to generate a report.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-page-object-builder

Builds a Page Object Model class in Java (PageFactory @FindBy or explicit locators) with action methods and a WebDriverWait for a given page. Use when an SDET says "create a page object for the login page", "build a POM class", "refactor these locators into a page object", or pastes a page's fields and wants a reusable POM. Produces a draft class the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-locator-strategist

Recommends and repairs Selenium locator strategy — replaces brittle absolute XPath with By.id, By.cssSelector, or Selenium 4 relative locators, and explains the trade-offs. Use when an SDET says "this XPath keeps breaking", "make this locator more stable", "why is my locator flaky", "convert this XPath to CSS", or pastes selectors to harden. Produces proposals the engineer must verify in the DOM.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-grid-configurator

Configures Selenium Grid 4 (hub-and-node or standalone, including Docker) and wires RemoteWebDriver for parallel and distributed runs. Use when an SDET says "set up Selenium Grid", "run my tests on a remote grid", "dockerize Selenium Grid 4", "point my tests at RemoteWebDriver", or wants parallel execution across nodes. Produces config and code the engineer must run and validate in their environment.

★ 4