What problem does it solve? Running and debugging VS Code smoke tests involves knowing the right npm scripts, grep filters, and CI artifact layouts, and intermittent CI-only failures are especially hard to reproduce and diagnose without a systematic approach. ## Core Features & Use Cases - Smoke Test Execution: Run full end-to-end UI flows with npm run smoketest or smoketest-no-compile, filtering suites with mocha grep patterns and options like --tracing, --web, --remote, and --build. - Flaky Test Hunting: Apply a temporary repeat-loop technique in GitHub Actions or Azure DevOps pipelines that reruns a suspect suite many times and fails fast to capture traces and screenshots of intermittent failures. - CI Failure Diagnosis: Download and interpret smoke test log artifacts from GitHub Actions (gh run download) or Azure DevOps (az pipelines runs artifact download), including runner logs, Copilot runtime logs, extension-host logs, and Playwright screenshots. - Use Case: A smoke test fails only in CI on macOS. Add a temporary 20-iteration loop step to the PR workflow, reproduce the failure, download the logs-macos-arm64-electron-1 artifact, and inspect the Copilot runtime logs to find the timeout cause. ## Quick Start Run the smoke tests filtered to the Agents Window suite with tracing enabled using npm run smoketest.