GitHub Copilot for Azure 集成测试失败自动创建 Issue 工具 | 测试自动化

file-test-bug by microsoft/github-copilot-for-azure

451 周安装量

160 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/microsoft/github-copilot-for-azure --skill file-test-bug

自动化开发运维测试

🇨🇳中文介绍

文件测试错误

在 microsoft/github-copilot-for-azure 中为集成测试失败创建 GitHub issue。

输入

技能名称（必填）：例如 azure-rbac、appinsights-instrumentation
测试运行（可选）：测试运行的时间戳。默认为该技能最近一次有日志的测试运行。

步骤

如果未提供技能名称，则向用户询问
解析 tests/reports/junit.xml 以查找与该技能匹配的失败项
找到测试运行目录（指定的或最近有匹配日志的）
从 tests/reports/test-run-<timestamp>/<skillname>-<testname>/ 读取 agent-metadata.md
对于每个失败项，使用 junit.xml 中的位置信息（文件:行号）从测试文件中读取实际的代码行
必需 - 在创建 issue 前先进行诊断分析：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

255,700 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

136,300 周安装

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

98,500 周安装

repo: github-copilot-for-azure
title: <skill-name> 中的集成测试失败
labels: ["bug", "integration-test"]
body: |
  ## 失败的测试
  - <test-name>: <error message>
  
  ## 诊断分析
  
  ### 根本原因
  <基于 agent-metadata.md 分析，用 1-2 句话解释测试失败的原因>
  
  ### 各测试分析
  - **<test-name>**: <代理实际做了什么 vs 测试期望什么>
  
  ### 建议的修复方案
  <其中之一：更新技能、更新测试断言、提供测试夹具>

  ## 详细信息
  ### <test-name>
  **错误:** <来自 junit.xml 的失败信息>
  **位置:** <文件:行号>
  ```typescript
  <从指定行号的测试文件中读取的实际代码行>

🇺🇸English

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>

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 Installs

451

Repository

microsoft/githu…or-azure

GitHub Stars

160

First Seen

Feb 4, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykFail

Installed on

codex336

gemini-cli332

opencode302

cursor295

github-copilot294

kimi-cli291