file-test-bug

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-/-/ 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 labels: ["bug", "integration-test"] body: | ## Failed Tests - : ## Diagnosis ### Root Cause <1-2 sentences explaining WHY the test failed based on agent-metadata.md analysis> ### Analysis per Test - : ### Suggested Fix <one of: update skill, update test assertions, provide test fixtures> ## Details ### Error: Location: file:line ```typescript <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 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