Agent skill · software engineering · microsoft
integration-tests
Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.
Why this skill is useful
Adds detailed scripts and specific command options for running integration tests in the VS Code repo that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
Running Integration Tests Integration tests in VS Code are split into two categories: 1. Node.js integration tests - files ending in .integrationTest.ts under src/. These run in Electron via the same Mocha runner as unit tests. 2. Extension host tests - tests embedded in built-in extensions under extensions/ (API tests, Git tests, TypeScript tests, etc.). These launch a full VS Code instance with --extensionDevelopmentPath. Scripts macOS / Linux: ./scripts/test-integration.sh [options] Windows: .\scripts\test-integration.bat [options] When run without filters, both scripts execute all node.js integration tests followed by all extension host tests. They do not run the deterministic Agent Host E2E suites: those run with ./scripts/test-agent-host-e2e.sh (or .\scripts\test-agent-host-e2e.bat, or pnpm run test-agent-host-e2e), which runs each suite in its own isolated test process, in parallel. GitHub CI runs them in parallel with the integration tests, in the separate Linux / Agent-Host-E2E job on Linux and the Windows / Agent-Host-E2E (shard 1/3) through Windows / Agent-Host-E2E (shard 3/3) jobs on Windows, and as a separate step before 🧪 Run integration tests (Electron) on macOS; ADO runs them as the integration-agent-host-e2e test ID in a separate Agent Host E2E Tests (Electron) job, not in the Integration Tests (Electron) job (integration-electron). See src/vs/platform/agentHost/test/node/e2e/README.md. --run still accepts a single Agent Host E2E file. When run with --run or --runGlob (without --suite), only the node.js integration tests are run and the filter is applied. Extension host tests are skipped since these filters are node.js-specific. When run with --grep alone (no --run, --runGlob, or --suite), all tests are run -- both node.js integration tests and all extension host suites -- with the grep pattern forwarded to every test runner. When run with --suite, only the matching extension host test suites are run. Node.js integration tests are skipped. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/integration-tests