Test Report Writing

Name: Test Report Writing
Availability: InStock
Author: ductoanoxo

Consolidates API, K6, and frontend test outputs into a standardized Markdown report.

3|Updated May 3, 2026

Search Tags:#quality assurance #test reporting #markdown template #api integration testing #k6 performance #frontend ui testing

Ready to run

npx skills add https://github.com/ductoanoxo/Agent_SQL --skill test-report-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Test Report Writing
Source: https://github.com/ductoanoxo/Agent_SQL/tree/main/.agents/skills/testing/test-reporting
Command: npx skills add https://github.com/ductoanoxo/Agent_SQL --skill test-report-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of consolidating scattered API, performance, and frontend test outputs into a single standardized Markdown Test Report.

Core Features & Use Cases

Consolidate multi-source results: Pulls API Integration pass/fail counts and error lists, K6 performance metrics, and frontend UI/UX bugs/warnings from the expected output files.
Populate a standardized reporting template: Fills every required field in the Markdown report (mirroring a typical Excel test-report form), ensuring no section is left empty.
Produce a ready-to-submit artifact: Writes the completed report to .agents/agents/test-reporting/output/test_report.md with all missing values set to N/A.

Quick Start

Ask the AI to read the API integration results, K6 performance summary JSON, and the frontend test report, then generate the filled test_report.md at .agents/agents/test-reporting/output/test_report.md using the provided template.

Frequently Asked Questions about Test Report Writing

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

FAQPage Schema

How do I consolidate API, K6 performance, and frontend UI test results into a single report?▼

To consolidate API, K6 performance, and frontend UI test results into a single Markdown test report, you extract pass/fail counts, timing percentiles, and UI bugs, then populate a standardized template with all missing fields set to N/A.

What is the best way to generate a standardized test report from k6_summary.json and frontend test outputs?▼

The best way to generate a standardized test report from k6_summary.json and frontend outputs is to derive throughput and timing percentiles from the K6 data, capture frontend bug references, and write them into a unified Markdown file.

Does test report generation support end-to-end testing scenarios for specific build versions?▼

Test report generation supports end-to-end testing scenarios by creating an auditable summary of correctness, responsiveness, and user-facing defects specifically tailored for a given build version and environment.

How do I handle missing values when filling out a Markdown test reporting template?▼

When filling out a Markdown test reporting template, you handle missing values by setting all unfilled fields to N/A, ensuring the final test report artifact remains standardized and completely populated.

Why do I need to consolidate scattered API integration outcomes and frontend UI bugs into Markdown?▼

Consolidating scattered API integration outcomes and frontend UI bugs into Markdown removes manual effort, producing a ready-to-submit, auditable artifact that mirrors typical Excel test-report forms for your build.