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 E2E Tests

by microsoft in microsoft/vscode-python-environments

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

OfficialMITAuto-check passedTesting & QA

Install Run E2E Tests

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

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

GitHub CLI
$ gh skill install microsoft/vscode-python-environments run-e2e-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-e2e-tests .claude/skills/run-e2e-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-e2e-tests
GitHub stars
141
Token cost
~1.2k tokens
SKILL.md length
337 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

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

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

What it does

Run E2E Tests is an agent skill from microsoft/vscode-python-environments, published by the product's own GitHub organization. Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major changes.

Its SKILL.md is about 1.2k 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 End-to-end testing. It works with Visual Studio Code, npm and Python. 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 End-to-end testing

Example prompts

  • “/run-e2e-tests”

Requirements

  • Python 3

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 E2E Tests loads about 1.2k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 337 words of instructions outside code blocks.

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

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). 337 words, ~1,157 tokens.

Download SKILL.mdSave it as .claude/skills/run-e2e-tests/SKILL.md (or your agent's skills folder).
name
run-e2e-tests
description
Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major changes.

Run E2E (end-to-end) tests to verify complete user workflows work correctly.

When to Use This Skill

  • Before submitting a PR with significant changes
  • After modifying environment discovery, creation, or selection logic
  • Before a release to validate full workflows
  • When user reports a workflow is broken

Note: Run smoke tests first. If smoke tests fail, E2E tests will also fail.

Quick Reference

ActionCommand
Run all E2E testsnpm run compile && npm run compile-tests && npm run e2e-test
Run specific testnpm run e2e-test -- --grep "discovers"
Debug in VS CodeDebug panel → "E2E Tests" → F5

How E2E Tests Work

Unlike unit tests (mocked) and smoke tests (quick checks), E2E tests:

  1. Launch a real VS Code instance with the extension
  2. Exercise complete user workflows via the real API
  3. Verify end-to-end behavior (discovery → selection → execution)

They take longer (1-3 minutes) but catch integration issues.

Workflow

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

Pass:

  E2E: Environment Discovery
    ✓ Can trigger environment refresh
    ✓ Discovers at least one environment
    ✓ Environments have required properties
    ✓ Can get global environments

  4 passing (45s)

Fail: Check error message and see Debugging section.

Debugging Failures

ErrorCauseFix
No environments discoveredPython not installedInstall Python, verify it's on PATH
Extension not foundBuild failedRun npm run compile
API not availableActivation errorDebug with F5, check Debug Console
Timeout exceededSlow operation or hangIncrease timeout or check for blocking code

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

Prerequisites

E2E tests have system requirements:

  • Python installed - At least one Python interpreter must be discoverable
  • Extension builds - Run npm run compile before tests
  • CI needs webpack build - Run npm run compile (webpack) before tests, not just npm run compile-tests (tsc)

Adding New E2E Tests

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

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

suite('E2E: [Workflow Name]', function () {
    this.timeout(120_000); // 2 minutes

    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('[Test description]', async function () {
        // Use real API (flat structure, not nested!)
        // api.getEnvironments(), not api.environments.getEnvironments()
        await waitForCondition(
            async () => (await api.getEnvironments('all')).length > 0,
            60_000,
            'No environments found',
        );
    });
});

Test Files

FilePurpose
src/test/e2e/environmentDiscovery.e2e.test.tsDiscovery workflow tests
src/test/e2e/index.tsTest runner entry point
src/test/testUtils.tsUtilities (waitForCondition, etc.)

Notes

  • E2E tests are slower than smoke tests (expect 1-3 minutes)
  • They may create/modify files - cleanup happens in suiteTeardown
  • First run downloads VS Code (~100MB, cached in .vscode-test/)
  • For more details on E2E tests and how they compare to other test types, refer to the project's testing documentation.

© 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-e2e-tests of microsoft/vscode-python-environments.

Open the folder on GitHubat commit 4faeedf

Compare with similar skills

Run E2E 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 E2E Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run E2E Tests this skillmicrosoft/vscode-python-environments141—~1.2kAutomated safety check: PassMIT
Blockless Extension E2EFreakStudioCN/mpy-hardware-extension118—~1.2kAutomated safety check: NotesCustom licence
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Acarshub Tool Additionssdr-enthusiasts/docker-acarshub117—~707Automated safety check: PassGPL-3.0
Rocky Devrocky-data/rocky304—~2.1kAutomated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0

Similar skills

  • 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

  • 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

  • Acarshub Tool Additions

    sdr-enthusiasts/docker-acarshub

    Use ONLY when working in the docker-acarshub repository AND a task may require adding a system tool, npm package, or other dependency.

    117 GitHub stars~707 tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Rocky Dev

    rocky-data/rocky

    Top-level router for Rocky development tasks. An agent skill from rocky-data/rocky.

    304 GitHub stars~2.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Qwen Code E2E Testing

    QwenLM/qwen-code

    Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.

    28k GitHub stars~2.1k tokensUpdated yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

  • Run Integration Tests

    microsoft/vscode-python-environments

    Official

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

    141 GitHub stars~1.1k tokensUpdated yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Works with

Categories

Questions about Run E2E Tests

What does Run E2E Tests do?

Run E2E tests to verify complete user workflows like environment discovery, creation, and selection. Run E2E Tests is an agent skill from microsoft/vscode-python-environments, published by the product's own GitHub organization. Run E2E tests to verify complete user workflows like environment discovery, creation, and selection.

When should I use Run E2E Tests?

Run E2E Tests fits situations like: tasks that involve End-to-end testing.

How do I install Run E2E Tests in Claude Code?

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

How do I install Run E2E Tests in Codex?

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

Can I use Run E2E 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-e2e-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-e2e-tests, .gemini/skills/run-e2e-tests, .github/skills/run-e2e-tests and .opencode/skills/run-e2e-tests in your project.

What does Run E2E Tests need to run?

Going by SKILL.md and its folder, Run E2E Tests needs the command-line tools its instructions call (npm). Our summary lists: Python 3.

Does Run E2E 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 E2E 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 E2E Tests use?

Run E2E 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 E2E Tests use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 E2E Tests?

Skills that share tags, products or a category with Run E2E Tests: Blockless Extension E2E (FreakStudioCN/mpy-hardware-extension, 118 stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Acarshub Tool Additions (sdr-enthusiasts/docker-acarshub, 117 stars) and Rocky Dev (rocky-data/rocky, 304 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run E2E 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.