New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Run Integration Tests

by microsoft in microsoft/vscode-python-environments

Run integration tests to verify that extension components work together correctly.

OfficialMITAuto-check passedTesting & QA

Install Run Integration Tests

skills CLI
$ npx skills add microsoft/vscode-python-environments --skill run-integration-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/vscode-python-environments run-integration-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/vscode-python-environments.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/run-integration-tests .claude/skills/run-integration-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-integration-tests
GitHub stars
141
Token cost
~1.1k tokens
SKILL.md length
285 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Run integration tests to verify that extension components work together correctly.

  • Works in 2 steps: Compile and Run → Interpret Results
  • Tasks that involve Integration testing
  • SKILL.md covers When to Use This Skill, Quick Reference, How Integration Tests Work and Workflow, plus 5 more sections
  • Calls npm

What it does

Run Integration Tests is an agent skill from microsoft/vscode-python-environments, published by the product's own GitHub organization. Run integration tests to verify that extension components work together correctly. Use this after modifying component interactions or event handling.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Integration testing. It works with Visual Studio Code and npm. The repository describes itself as: VS Code extension for Python environment and package management. The licence is MIT.

When your agent uses it

  • Tasks that involve Integration testing

Example prompts

  • “/run-integration-tests”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Compile and Run
  2. Interpret Results

What it can do on your machine

Read from SKILL.md and the folder at commit 4faeedf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Integration Tests loads about 1.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/vscode-python-environments at commit 4faeedf, republished under its MIT licence (© microsoft). 285 words, ~1,072 tokens.

Download SKILL.mdSave it as .claude/skills/run-integration-tests/SKILL.md (or your agent's skills folder).
name
run-integration-tests
description
Run integration tests to verify that extension components work together correctly. Use this after modifying component interactions or event handling.

Run integration tests to verify that multiple components (managers, API, settings) work together correctly.

When to Use This Skill

  • After modifying how components communicate (events, state sharing)
  • After changing the API surface
  • After modifying managers or their interactions
  • When components seem out of sync (UI shows stale data, events not firing)

Quick Reference

ActionCommand
Run all integration testsnpm run compile && npm run compile-tests && npm run integration-test
Run specific testnpm run integration-test -- --grep "manager"
Debug in VS CodeDebug panel → "Integration Tests" → F5

How Integration Tests Work

Integration tests run in a real VS Code instance but focus on component interactions:

  • Does the API reflect manager state?
  • Do events fire when state changes?
  • Do different scopes return appropriate data?

They're faster than E2E (which test full workflows) but more thorough than smoke tests.

Workflow

Step 1: Compile and Run
bash
npm run compile && npm run compile-tests && npm run integration-test
Step 2: Interpret Results

Pass:

  Integration: Environment Manager + API
    ✓ API reflects manager state after refresh
    ✓ Different scopes return appropriate environments
    ✓ Environment objects have consistent structure

  3 passing (25s)

Fail: Check error message and see Debugging section.

Debugging Failures

ErrorCauseFix
API not availableExtension activation failedCheck Debug Console
Event not firedEvent wiring issueCheck event registration
State mismatchComponents out of syncAdd logging, check update paths
TimeoutAsync operation stuckCheck for deadlocks

For detailed debugging: Debug panel → "Integration Tests" → F5

Adding New Integration Tests

Create files in src/test/integration/ with pattern *.integration.test.ts:

typescript
import * as assert from 'assert';
import * as vscode from 'vscode';
import { waitForCondition, TestEventHandler } from '../testUtils';
import { ENVS_EXTENSION_ID } from '../constants';

suite('Integration: [Component A] + [Component B]', function () {
    this.timeout(120_000);

    let api: ExtensionApi;

    suiteSetup(async function () {
        const extension = vscode.extensions.getExtension(ENVS_EXTENSION_ID);
        assert.ok(extension, 'Extension not found');
        if (!extension.isActive) await extension.activate();
        api = extension.exports;
    });

    test('[Interaction test]', async function () {
        // Test component interaction
    });
});

Test Files

FilePurpose
src/test/integration/envManagerApi.integration.test.tsManager + API tests
src/test/integration/index.tsTest runner entry point
src/test/testUtils.tsUtilities (waitForCondition, TestEventHandler)

Prerequisites

  • CI needs webpack build - Run npm run compile (webpack) before tests, not just npm run compile-tests (tsc)
  • Extension builds - Run npm run compile before tests

Notes

  • Integration tests are faster than E2E (30s-2min vs 1-3min)
  • Focus on testing component boundaries, not full user workflows
  • First run downloads VS Code (~100MB, cached in .vscode-test/)

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/run-integration-tests of microsoft/vscode-python-environments.

Open the folder on GitHubat commit 4faeedf

Compare with similar skills

Run Integration Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Integration Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Integration Tests this skillmicrosoft/vscode-python-environments141—~1.1kAutomated safety check: PassMIT
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Interactive CLI Testing With tui-testslopus/happy24k—~603Automated safety check: PassMIT
Promotion Branches E2E Testhardisgroupcom/sfdx-hardis400—~4.7kAutomated safety check: NotesAGPL-3.0
Running TestsNangoHQ/nango13k—~876Automated safety check: PassCustom licence
Blockless Extension E2EFreakStudioCN/mpy-hardware-extension118—~1.2kAutomated safety check: NotesCustom licence

Similar skills

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

  • Interactive CLI Testing With tui-test

    slopus/happy

    Tests interactive CLI and TUI programs with Microsoft's tui-test, driving prompts, arrow keys and screen output in a real pseudo-terminal.

    24k GitHub stars~603 tokensUpdated today
    Testing & QAAuto-check passed

  • Promotion Branches E2E Test

    hardisgroupcom/sfdx-hardis

    Runs a full end-to-end test of sfdx-hardis promotion branches and backpromote against real Salesforce orgs and a throwaway repository, then writes a report.

    400 GitHub stars~4.7k tokensUpdated today
    Testing & QAAuto-check: notes

  • Running Tests

    NangoHQ/nango

    A skill your agent uses when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns

    13k GitHub stars~876 tokensUpdated today
    Testing & QAAuto-check passed

  • Blockless Extension E2E

    FreakStudioCN/mpy-hardware-extension

    Run and debug the Blockless VS Code extension release gate: CI-equivalent API and extension tests, V0 protocol smoke, live DeepSeek full-stack e2e, VSIX packaging, local reinstall, direct…

    118 GitHub stars~1.2k tokensUpdated 9 days ago
    Testing & QAAuto-check: notes

  • MCP Testing

    adeze/raindrop-mcp

    MCP Testing Strategies with Vitest, Inspector, and Integration Tests

    188 GitHub stars~1.6k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

More from microsoft/vscode-python-environments

All 9 skills in this repo

  • Cross Platform Paths

    microsoft/vscode-python-environments

    Official

    Critical patterns for cross-platform path handling in this VS Code extension.

    141 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Python Manager Discovery

    microsoft/vscode-python-environments

    Official

    Environment manager-specific discovery patterns and known issues.

    141 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Run E2E Tests

    microsoft/vscode-python-environments

    Official

    Run E2E tests to verify complete user workflows like environment discovery, creation, and selection.

    141 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Run Smoke Tests

    microsoft/vscode-python-environments

    Official

    Run smoke tests to verify extension functionality in a real VS Code environment.

    141 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Debug Failing Test

    microsoft/vscode-python-environments

    Official

    Debug a failing test using an iterative logging approach, then clean up and document the learning.

    141 GitHub stars~780 tokensUpdated today
    Auto-check passed

  • Generate Snapshot

    microsoft/vscode-python-environments

    Official

    Generate a codebase health snapshot for technical debt tracking and planning.

    141 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Run Integration Tests

What does Run Integration Tests do?

Run integration tests to verify that extension components work together correctly. Run Integration Tests is an agent skill from microsoft/vscode-python-environments, published by the product's own GitHub organization. Run integration tests to verify that extension components work together correctly.

When should I use Run Integration Tests?

Run Integration Tests fits situations like: tasks that involve Integration testing.

How do I install Run Integration Tests in Claude Code?

Run `npx skills add microsoft/vscode-python-environments --skill run-integration-tests -a claude-code`. Or copy the skill folder (.github/skills/run-integration-tests in microsoft/vscode-python-environments) into .claude/skills/run-integration-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Integration Tests in Codex?

Run `npx skills add microsoft/vscode-python-environments --skill run-integration-tests -a codex`. Or copy the skill folder (.github/skills/run-integration-tests in microsoft/vscode-python-environments) into .agents/skills/run-integration-tests in your project. Codex loads it when a task matches its description.

Can I use Run Integration Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/vscode-python-environments --skill run-integration-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-integration-tests, .gemini/skills/run-integration-tests, .github/skills/run-integration-tests and .opencode/skills/run-integration-tests in your project.

What does Run Integration Tests need to run?

Going by SKILL.md and its folder, Run Integration Tests needs the command-line tools its instructions call (npm).

Does Run Integration Tests access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run Integration Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Integration Tests use?

Run Integration Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Integration Tests use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Integration Tests?

Skills that share tags, products or a category with Run Integration Tests: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Interactive CLI Testing With tui-test (slopus/happy, 24k stars), Promotion Branches E2E Test (hardisgroupcom/sfdx-hardis, 400 stars) and Running Tests (NangoHQ/nango, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Integration Tests?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/vscode-python-environments, which has 141 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: microsoft/vscode-python-environments on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.