skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

file-test-bug

File GitHub issues for local integration test failures from junit.xml.

242|189|Updated Oct 28, 2024
Search Tags:#automation#github#integration-testing#junit#issue-creation#agent-metadata
One-click install
npx skills add https://github.com/microsoft/GitHub-Copilot-for-Azure --skill file-test-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-test-bug
Source: https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/.github/skills/file-test-bug
Command: npx skills add https://github.com/microsoft/GitHub-Copilot-for-Azure --skill file-test-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of GitHub issues to document local integration test failures, ensuring issues are consistently created with relevant context and traceability.

Core Features & Use Cases

  • Automatically parse local test reports (junit.xml) and map failures to the correct test run.
  • Extract contextual details from agent-metadata.md to generate informative, reproducible issues.
  • Create standardized issues in microsoft/github-copilot-for-azure with diagnostics, failure location, and suggested fixes.

Quick Start

Ask the skill to file an issue for a specific failing test by providing the test name and optional failure details. The skill will locate the most recent test run with matching logs, extract the failure context, and open a new issue in the microsoft/github-copilot-for-azure repository.

Frequently Asked Questions about file-test-bug

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

FAQPage Schema
How do I auto-create GitHub issues for JUnit integration test failures?▼

To auto-create GitHub issues for integration test failures, this skill parses local junit.xml files to identify failures and generates standardized issues. It automatically extracts failure context and files the issue directly in the repository.

What context is needed to automatically file a GitHub issue for a failing test?▼

Filing a GitHub issue for a failing test requires junit.xml test reports and agent-metadata.md files. The skill reads these inputs to locate the specific test run directory and extract the necessary diagnostic context for the issue.

Can I use this to document CI workflow test failures as GitHub issues?▼

Yes, you can use this skill to document CI workflow test failures as GitHub issues. It applies to both local test runs and CI workflows, ensuring integration test failures are consistently documented with full traceability.

How do I generate standardized GitHub issues from local test run directories?▼

You generate standardized GitHub issues by asking the skill to file an issue for a specific failing test. It locates the most recent matching test run directory, reads the agent-metadata.md for context, and creates a reproducible issue using a template.

What is the best way to track local integration test failures in a GitHub repository?▼

The best way to track local integration test failures is automating issue creation with this skill. It maps JUnit report failures to the correct test run, extracts diagnostics, and opens a standardized issue in the microsoft/github-copilot-for-azure repository.

Related Skills

Explore More Software Engineering Skills→
polsegupolsegu

test-flakiness

Detect nondeterministic failures by parsing CI logs and aggregating per-test pass/fail histories.

Community
Intermediate
pmcdowallpmcdowall

github-issues

Create, organize, and resolve GitHub issues via CLI or REST API.

Community
Intermediate
databrickslabsdatabrickslabs
38

bdd-run

Execute Behave BDD test suites with tag filtering and JUnit/JSON reports.

Official
Advanced
microsoftmicrosoft
242

file-test-bug

File GitHub issues for local integration test failures from junit.xml.

Official
Intermediate