vitest-extension-testing

Run and debug Vitest tests for the claude-skills-deployer VS Code extension.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill vitest-extension-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vitest-extension-testing
Source: https://github.com/sergeyitaly/claude-skill-deployer/tree/main/skills_library/vitest-extension-testing
Command: npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill vitest-extension-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and friction of running, debugging, and interpreting Vitest test results for the claude-skills-deployer VS Code extension, saving developers time troubleshooting test failures and inconsistent test execution.

Core Features & Use Cases

  • Standardized Test Execution: Clear naming conventions and run commands for all extension test types including unit tests, latency benchmarks, solo parallel-safe tests, data pruning tests, and VS Code Extension Host integration tests.
  • Common Failure Troubleshooting: Step-by-step fixes for frequent issues like missing vscode module errors, compilation resolution failures, missing xvfb on Linux/WSL, benchmark p95 regressions, and parallel test timeouts.
  • Use Case: When refactoring the extension's MCP filesystem server, use this Skill to quickly run the relevant benchmark tests, interpret p95 latency results, and identify blocking I/O issues in the hot path.

Quick Start

Use the vitest-extension-testing skill to run all unit tests for the claude-skills-deployer extension and interpret any failure outputs to resolve issues quickly.

Frequently Asked Questions about vitest-extension-testing

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

FAQPage Schema
How do I run Vitest unit tests for a VS Code extension?▼

Run Vitest unit tests for a VS Code extension using standardized run commands covering unit tests, latency benchmarks, solo parallel-safe tests, and Extension Host integration, then interpret failure outputs to resolve issues quickly.

Why does my VS Code extension test fail with a missing vscode module error?▼

A missing vscode module error occurs during extension testing when the VS Code Extension Host environment is not properly configured. Follow step-by-step troubleshooting to resolve compilation failures and missing module issues.

What is a solo parallel-safe test in Vitest extension development?▼

A solo parallel-safe test in Vitest is a test designed to run safely in parallel without interfering with others. It is a specific extension test type covered alongside data pruning and latency benchmark tests.

How do I troubleshoot p95 latency regressions in Vitest benchmark tests?▼

Troubleshoot p95 latency regressions in Vitest benchmark tests by running the relevant benchmarks, interpreting p95 latency results, and identifying blocking I/O issues in the hot path to pinpoint performance bottlenecks.

Do I need xvfb to run VS Code Extension Host integration tests on Linux?▼

You need xvfb on Linux or WSL to run VS Code Extension Host integration tests, as missing xvfb is a common failure. Step-by-step fixes are provided for this and other parallel test timeout issues.