integration-tests

Runs VS Code integration tests with filtering options for node.js and extension host suites.

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill integration-tests-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-tests
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/integration-tests
Command: npx skills add https://github.com/Niiihuel/openide --skill integration-tests-niiihuel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running integration tests in the VS Code repository involves two distinct test types (node.js integration tests and extension host tests) with different scripts, filters, and behaviors, making it easy to invoke the wrong runner or apply filters incorrectly. ## Core Features & Use Cases - Dual Test Category Support: Distinguishes node.js integration tests (.integrationTest.ts under src/) from extension host tests embedded in built-in extensions, and explains how each is executed. - Filtering Options: Documents --run, --runGlob, --grep, and --suite flags, including how they interact (e.g., --suite skips node.js tests, --grep alone applies to all runners). - Use Case: A developer modifying the search service can run ./scripts/test-integration.sh --run src/vs/workbench/services/search/test/browser/search.integrationTest.ts to execute only the relevant integration test file instead of the full suite. ## Quick Start Run the integration tests for the Git extension by asking the agent to execute scripts/test-integration.sh with the --suite git option.

Frequently Asked Questions about integration-tests

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

FAQPage Schema
How do I run integration tests in the VS Code repo?▼

Run ./scripts/test-integration.sh on macOS/Linux or .\scripts\test-integration.bat on Windows. Without filters, this executes all node.js integration tests followed by all extension host test suites.

How do I run a single VS Code integration test file?▼

Pass the source file path with --run, for example ./scripts/test-integration.sh --run src/vs/workbench/services/search/test/browser/search.integrationTest.ts. This runs only that file's node.js integration tests and skips extension host tests.

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

Unit tests use .test.ts files and run via scripts/test.sh, while integration tests use .integrationTest.ts files or extension host tests and run via scripts/test-integration.sh. The two scripts are not interchangeable.

How do I run only specific extension host test suites?▼

Use the --suite option with a suite name, comma-separated list, or glob pattern, such as --suite git or --suite 'git,typescript,emmet'. Node.js integration tests are skipped when --suite is used.

Why do VS Code integration tests fail before running?▼

Integration tests run against compiled JavaScript output, so the VS Code - Build watch task must be running or compilation must have completed first. Running tests against stale or missing build output causes failures.