qa-test-reporting
Test reporting and coverage analytics: JUnit XML, LCOV and Cobertura parsing, Allure reports, coverage diffs, and test run summaries for pull requests. Also covers JaCoCo and coverage.py analysis, risk-ranked coverage targets, TestRail / Xray / Zephyr Scale result sync, and Currents analytics. Agents (daily-test-suite-aggregator, release-quality-report-agent) roll up daily results across suites and assemble a release-quality go / no-go report. Jest and Vitest coverage lives in qa-unit-tests-js.
/plugin install qa-test-reporting@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Foundations
- Version
v1.6.10- Contents
- 10 skills · 2 agents
Skills10
allure-reportsUse when a team wants richer test reports than JUnit XML: steps, attachments, per-test history, retries and severity or feature labels.skillcoverage-diff-reporterUse when a pull request needs readable coverage feedback rather than one total.skillcoverage-py-analysisUse when a Python project (pytest or unittest) needs code coverage: coverage run, branch coverage, combining parallel xdist data, .coveragerc source, omit and fail_under settings, and terminal, HTML, Cobertura XML, LCOV or JSON reports for CI.skillcurrents-integrationUse when a Playwright suite needs hosted analytics across runs: flakiness over time, slowest tests and pass-rate trends.skilljacoco-analysisUse whenever a Java, Kotlin, Scala or Groovy project on Gradle or Maven needs code coverage or a coverage gate: JaCoCo agent setup, HTML, XML and CSV reports, check rules that fail the build below a minimum such as 80% lines, the six counters, and JaCoCo XML to LCOV or Cobertura.skilljunit-xml-analysisExplains CI test numbers that disagree with what the suite actually did - a 'slowest tests' list dominated by the wrong suite, a release gate or dashboard reading only the summary attributes on the suite element and never the cases below them, or a pass rate that quietly counts skipped tests as passes.skilllcov-analysisUse when a coverage gate must work across languages from LCOV .info or Cobertura XML files (gcov, llvm-cov, coverage.py, JaCoCo, Jest, nyc, coverlet).skilltest-coverage-targeterUse when a team can write only a handful of new tests and must pick which uncovered code matters most, or when some modules lose coverage while the total looks fine.skilltest-management-syncUse when CI test results must flow into TestRail, Xray for Jira or Zephyr Scale without manual copying.skilltest-run-summary-authorUse whenever someone asks to write a test-run summary, release test status or Slack post from test results, even from a few numbers: pass, fail and skip counts, JUnit XML, Allure JSON, a TestRail, Xray or Zephyr export.skill
Agents2
daily-test-suite-aggregatorAction-taking agent that ingests test-run artifacts from multiple suites (unit, integration, E2E, contract, performance, accessibility) and multiple environments (dev, staging, prod-canary) for a single day and emits a unified cross-suite cross-environment summary suitable for the team stand-up.agentrelease-quality-report-agentAction-taking agent that assembles an evidence-backed release-quality go/no-go report for QA managers and heads of engineering by composing a test-run narrative, a per-file coverage diff, and risk-ranked coverage targets into a single manager-facing document with an explicit GO / NO-GO / CONDITIONAL verdict.agent
About qa-test-reporting
Test reporting + coverage analytics: per-format parsers (JUnit XML, LCOV + Cobertura, Allure), build-an-X PR reporters (coverage delta, run-summary narrative), the test-management-sync umbrella (TestRail / Xray / Zephyr) plus Currents analytics, per-language coverage analyzers (JaCoCo, coverage.py; Jest/Vitest coverage lives in qa-unit-tests-js), and a risk-weighted coverage-targeting heuristic with a coverage debt ledger.