test-report

Generate test execution reports documenting results, defects, coverage, and release recommendations.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill test-report-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-report
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/quality/test-report
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill test-report-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a test cycle, QA teams must consolidate execution results, defect data, and coverage metrics into a report that supports go/no-go release decisions. Doing this manually is slow and error-prone, and inconsistent reports undermine stakeholder trust. ## Core Features & Use Cases - Structured Report Generation: Produces a complete test report with execution summary, results by module, defect analysis, coverage metrics, and entry/exit criteria assessment. - Release Recommendation: Includes a justified GO / NO-GO / CONDITIONAL GO recommendation with risk assessment and known issues going to production. - Governance Integration: Enforces validation rules, signature gating by the QA Lead, and a sources file tracking question history and information gaps. - Use Case: After completing a regression cycle on build 2.4.0, generate a signed test report summarizing pass rates, open critical defects, and a release recommendation for the steering committee. ## Quick Start Ask the agent to generate the test report for the current project using the signed test cases and defect log from the completed test cycle.

Frequently Asked Questions about test-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a test execution report for a release decision?▼

Provide the project name, test cycle, build version, environment, and execution results. The skill produces a report with execution summary, defect analysis, coverage metrics, and a justified GO or NO-GO recommendation.

What inputs are required to create a test report?▼

The skill requires signed test cases from the test-cases skill, a signed defect log from the defect-log skill, the test plan, and execution results including pass/fail counts per category.

What sections does a comprehensive test report include?▼

The report includes an executive summary, execution overview, results by module, defect summary and trends, coverage analysis, entry/exit criteria assessment, performance and security results, known issues, and a release recommendation.

Why is the test report blocked from generation?▼

Generation is blocked when prerequisite documents are not signed. Both the test-cases and defect-log documents must exist at their canonical paths and carry valid signatures before this skill runs.

Who approves the test report in this workflow?▼

The QA Lead holds final approval authority over the test report. The Product Owner and Technical Lead review content but do not gate the signature.