---
id: sm-file-test-bug
name: "file-test-bug"
url: https://skills.yangsir.net/skill/sm-file-test-bug
author: microsoft
domain: ai-code-generation-quality
tags: ["bug-reporting", "test-case-management", "software-testing", "azure-devops", "quality-assurance"]
install_count: 1046
rating: 4.30 (42 reviews)
github: https://github.com/microsoft/github-copilot-for-azure
---

# file-test-bug

> 利用GitHub Copilot for Azure辅助文件管理、测试编写和缺陷排查，提高开发效率。

**Stats**: 1,046 installs · 4.3/5 (42 reviews)

## Before / After 对比

### 集成测试失败问题报告自动化对比

| Metric | Before | After | Change |
|---|---|---|---|
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |

## Readme

# file-test-bug

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.xml for failures matching the skill Find test run directory (specified or most recent with matching logs) Read agent-metadata.md from tests/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.Weekly Installs251Repositorymicrosoft/githu…or-azureGitHub Stars156First SeenFeb 4, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykFailInstalled oncodex232gemini-cli228opencode200github-copilot195cursor194kimi-cli191

---
*Source: https://skills.yangsir.net/skill/sm-file-test-bug*
*Markdown mirror: https://skills.yangsir.net/api/skill/sm-file-test-bug/markdown*