smoke-tests

Runs VS Code end-to-end smoke tests and diagnoses flaky CI failures.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jimeh/hucode --skill smoke-tests-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-tests
Source: https://github.com/jimeh/hucode/tree/main/.github/skills/smoke-tests
Command: npx skills add https://github.com/jimeh/hucode --skill smoke-tests-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

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 hard to reproduce without a structured approach. ## Core Features & Use Cases - Test Execution: Run smoke tests via npm run smoketest or smoketest-no-compile, with grep filtering (-g), tracing, web/remote modes, and packaged-build targeting. - Flaky Test Hunting: Apply a temporary repeat-loop technique in GitHub Actions or Azure DevOps steps to reproduce intermittent CI failures and capture traces. - CI Log Analysis: Download and interpret smoke test log artifacts from GitHub Actions (gh run download) or Azure DevOps (az pipelines runs artifact download), including Copilot runtime logs and Playwright screenshots. - Use Case: A smoke suite fails only in CI. Add a temporary 20-iteration loop step targeting that suite with -g, push a throwaway branch, and inspect the failing run's traces and screenshots from the logs artifact. ## Quick Start Run the VS Code smoke tests filtered to a specific suite with tracing enabled and show me how to debug any failures from the CI logs artifact.

Frequently Asked Questions about smoke-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run VS Code smoke tests?▼

Run npm run smoketest to compile and execute the smoke tests, or npm run smoketest-no-compile to run already-compiled tests. Pass extra arguments after -- to the runner, such as -g to filter suites by title.

How do I run only a specific smoke test suite?▼

Use the -g (or -f) option with a substring of the suite title, for example npm run smoketest -- -g "Agents Window" --tracing. The pattern matches mocha test and suite titles, so one substring can select multiple related suites.

How do I reproduce a flaky smoke test that only fails in CI?▼

Add a temporary loop step in the CI workflow that runs the suspect suite 20 times with -g and --tracing, failing fast on the first error. Push it on a throwaway branch, then remove the loop before merging since it adds significant runtime.

How do I download smoke test logs from CI?▼

For GitHub Actions use gh run download <run-id> -n logs-<os>-<arch>-<suite>-<attempt>. For Azure DevOps use az pipelines runs artifact download with the run id and artifact name. Both artifacts share the same internal layout.

Why did my Copilot smoke test time out waiting for a response?▼

Check the copilot-runtime-logs/process-*.log files inside the suite folder of the logs artifact first. They record the Copilot CLI's startup, auth, model requests, and protocol errors, explaining timeouts the test error alone does not.

What is the difference between smoke tests, unit tests, and integration tests in VS Code?▼

Smoke tests in test/smoke/ drive a full VS Code instance through end-to-end UI flows via npm run smoketest. Unit tests (.test.ts) run via scripts/test.sh, and integration tests (.integrationTest.ts) run via scripts/test-integration.sh.