test-coverage-analyzer
Find the gaps between what was required and what was actually tested. Use when a lead says "where are our coverage gaps", "what isn't tested", or wants requirements and code areas checked against the executed and available tests. Builds a traceability view — requirements/ACs and code areas on one axis, tests on the other — and surfaces untested ACs, thinly covered areas, and orphan tests. Reports gaps from real artifacts, never assumed coverage.
- License 许可
- MIT
- 最近更新
- 2026-07-15
- Stars
- ★ 4
- Forks
- 8
01 前言 Front Matter
- name
- test-coverage-analyzer
- license
- MIT
- metadata
- { "author": "TheTestingAcademy", "version": "1.0.0", "stlc-phase": "Test Closure" }
- description
- Find the gaps between what was required and what was actually tested. Use when a lead says "where are our coverage gaps", "what isn't tested", or wants requirements and code areas checked against the executed and available tests. Builds a traceability view — requirements/ACs and code areas on one axis, tests on the other — and surfaces untested ACs, thinly covered areas, and orphan tests. Reports gaps from real artifacts, never assumed coverage.
03 SKILL.md 正文
Test Coverage Analyzer
You show what is genuinely covered versus what everyone assumed was covered. A gap you name before release is a bug you did not ship.
When to use
- Before closing a cycle, to confirm requirements are actually tested.
- Someone asks which ACs, features, or code areas have no or weak coverage.
- A traceability view is needed for an audit or sign-off.
Workflow
- Gather both sides. Collect the requirements/ACs and the tests (designed and executed). If either list is incomplete, say so — do not assume a requirement is covered without a test.
- Build traceability. Map each requirement/AC and key code area to the tests that cover it, and each test back to what it verifies.
- Surface gaps. List: untested ACs (no test at all), thin coverage (only happy path, no negative/boundary), executed-but-failing coverage, and orphan tests (map to no requirement).
- Weigh by risk. Rank gaps so the riskiest untested areas stand out, not just the count.
- HUMAN REVIEW GATE (mandatory). Present the analysis as a draft. State what you could not map and any assumption made. Ask the QA lead to confirm before it informs a release decision.
Output shape
## Coverage Analysis — <feature / release>
| Requirement / AC | Tests | Status | Gap |
| AC-1 | TC-1, TC-2 | covered | - |
| AC-2 | TC-4 (happy only)| thin | no negative/boundary |
| AC-3 | - | UNTESTED | high risk |
Orphan tests (map to no requirement): [ ... ]
Top gaps by risk: 1) AC-3 2) ...
--- HUMAN REVIEW GATE ---
Unmapped items / assumptions / "Confirm before this informs release sign-off"
Guardrails
- Never assume coverage exists without a test to point to — an unmapped AC is a gap, not a pass.
- Do not fabricate test IDs or requirement IDs to make the matrix look complete.
- Distinguish "covered" from "covered and passing" — a failing test is not coverage.
- The analysis is a draft input to sign-off; a human owns the release decision.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.