smoke-tests

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

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

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 systematic approach. ## Core Features & Use Cases - Test Execution: Run smoke tests via npm run smoketest or smoketest-no-compile, with grep filtering, tracing, and web/remote/headless modes. - Flaky Test Hunting: Apply a temporary repeat-loop technique in GitHub Actions or Azure DevOps 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 test fails intermittently only in CI. Add a temporary 20-iteration loop of the suspect suite to a throwaway branch, let CI reproduce the failure, then download the logs artifact to inspect the runner log and screenshots. ## 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 `--`, such as `-g "<suite name>"` to filter suites and `--tracing` to capture Playwright traces.

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

Add a temporary loop step to the CI workflow that runs the suspect suite 20 times with fail-fast on the first failure. Push it on a throwaway branch, let CI reproduce the flake with traces captured, and remove the loop before merging.

How do I download smoke test logs from GitHub Actions?▼

Use `gh run download <run-id> -n logs-<os>-<arch>-<suite>-<attempt> -D ./logs` with the run id from the workflow URL. The artifact contains the smoke-test-runner.log, per-suite extension host logs, and Playwright screenshots.

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`.

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

Check the Copilot runtime process logs under `<N>_suite_<Suite_Name>/copilot-runtime-logs/` in the logs artifact first. They record the SDK's startup, auth, model requests, and any protocol errors that explain timeouts the test error alone does not.