Bug_Reporting

Executes test cases and records observed failures as structured CSV bug reports.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/kainos-academy-2026/team4-frontend --skill bug-reporting-kainos-academy-2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bug_Reporting
Source: https://github.com/kainos-academy-2026/team4-frontend/tree/main/.github/skills/bug-reporting
Command: npx skills add https://github.com/kainos-academy-2026/team4-frontend --skill bug-reporting-kainos-academy-2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After test cases are written, teams still need to run them, compare actual behavior against expectations, and document defects in a consistent, triage-ready format. This Skill turns executed test cases into standardized CSV bug reports with severity, priority, and risk scoring, eliminating ad-hoc prose bug summaries. ## Core Features & Use Cases - Test Execution Workflow: Maps test cases to Vitest route tests, controller tests, service tests, mapper tests, view/template tests, and Supertest integration runs in a Node 22 Express/Nunjucks app. - Strict CSV Schema: Produces a fixed 9-column CSV (Title, Environment, Steps to Reproduce, Expected Result, Actual Result, Severity, Priority, Risk Score, Attachments/Evidence) with mandatory validation guardrails. - Risk Scoring Model: Calculates a numeric Risk Score by multiplying Severity and Priority values (Critical=4 through Low=1) for consistent defect triage. - Use Case: After generating test cases for a job-role listing feature, run the Sanity suite, discover that closed roles render in the list, and produce a CSV row with reproduction steps, environment details, severity High, priority High, risk score 9, and Vitest output as evidence. ## Quick Start Run the test cases from the Test_Cases output against this repo and generate a CSV bug report for any failures you observe.

Frequently Asked Questions about Bug_Reporting

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

FAQPage Schema
How do I convert test cases into a CSV bug report?

Execute each test case through the appropriate Vitest or Supertest path, compare actual behavior against the expected result, and log one CSV row per confirmed defect. Each row must contain title, environment, reproduction steps, expected and actual results, severity, priority, risk score, and evidence.

What columns does the bug report CSV format require?

The CSV requires exactly 9 columns in fixed order: Title, Environment, Steps to Reproduce, Expected Result, Actual Result, Severity, Priority, Risk Score, and Attachments/Evidence. Columns cannot be added, renamed, or reordered, and every row must parse to exactly 9 fields.

How is the bug risk score calculated from severity and priority?

Risk Score equals the Severity value multiplied by the Priority value, where Critical=4, High=3, Medium=2, and Low=1. For example, High severity with Medium priority yields a risk score of 6, and the numeric result is stored directly in the CSV.

Can I log passing test results in the bug report?

No, passing test cases should not produce bug rows unless a pass/fail execution log is explicitly requested. Blocked, unexecuted, or inconclusive tests are reported separately from confirmed defects in the summary.

What evidence should be attached to a bug report entry?

Attach factual, reproducible evidence such as failing Vitest output, HTTP response payloads, rendered HTML excerpts, stack traces, logs, or file references. Never invent evidence; if none was captured, state that the behavior was reproduced manually in the local environment.