file-test-bug▌
microsoft/github-copilot-for-azure · updated Apr 8, 2026
Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
File Test Bug
Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
Input
- Skill name (required): e.g.,
azure-rbac,appinsights-instrumentation - Test run (optional): Timestamp of test run. Defaults to most recent with logs for the skill.
Steps
- Ask user for skill name if not provided
- Parse
tests/reports/junit.xmlfor failures matching the skill - Find test run directory (specified or most recent with matching logs)
- Read
agent-metadata.mdfromtests/reports/test-run-<timestamp>/<skillname>-<testname>/ - For each failure, read the actual line of code from the test file using the location (file:line) from junit.xml
- REQUIRED - Write diagnosis BEFORE creating issue:
- Analyze the agent-metadata.md to understand what the agent did
- Compare agent behavior to what the test expected (from the assertion)
- Identify the root cause (skill issue, test issue, or model behavior)
- Write 2-3 sentences per failed test explaining WHY it failed
- Suggest potential fixes (update skill, update test, or update fixtures)
- Create issue via
github-mcp-server-create_issue:
owner: microsoft
repo: github-copilot-for-azure
title: Integration test failure in <skill-name>
labels: ["bug", "integration-test"]
body: |
## Failed Tests
- <test-name>: <error message>
## Diagnosis
### Root Cause
<1-2 sentences explaining WHY the test failed based on agent-metadata.md analysis>
### Analysis per Test
- **<test-name>**: <what agent did vs what test expected>
### Suggested Fix
<one of: update skill, update test assertions, provide test fixtures>
## Details
### <test-name>
**Error:** <failure from junit.xml>
**Location:** <file:line>
```typescript
<actual line of code from the test file at the specified line number>
<full contents of agent-metadata.md file, verbatim>
Important
Include the complete, unmodified contents of each agent-metadata.md file in the issue body. Do NOT summarize or truncate the logs. Wrap each log in a <details> block with the test name as the summary.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★34 reviews- ★★★★★Naina Ndlovu· Dec 16, 2024
Solid pick for teams standardizing on skills: file-test-bug is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Dec 4, 2024
file-test-bug is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 23, 2024
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Oct 14, 2024
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Min Lopez· Sep 25, 2024
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakshi Patil· Sep 21, 2024
file-test-bug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ishan Yang· Sep 9, 2024
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Alexander Haddad· Aug 28, 2024
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Min Flores· Aug 16, 2024
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Chaitanya Patil· Aug 12, 2024
file-test-bug has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 34