run-e2e-tests

Execute end-to-end tests for VS Code extension user workflows.

10|2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/mahmoud20138/Claude-Skills-Collection --skill run-e2e-tests-mahmoud20138
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-e2e-tests
Source: https://github.com/mahmoud20138/Claude-Skills-Collection/tree/main/05-VSCode-Extension-Skills/run-e2e-tests
Command: npx skills add https://github.com/mahmoud20138/Claude-Skills-Collection --skill run-e2e-tests-mahmoud20138

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that complete user workflows, from environment discovery to selection and execution, function correctly, preventing regressions and validating critical paths before releases.

Core Features & Use Cases

  • Comprehensive Workflow Validation: Tests the entire user journey, not just isolated components.
  • Pre-Release Assurance: Catches integration issues that unit or smoke tests might miss.
  • Use Case: Before deploying a new version of the VS Code extension, run these tests to confirm that users can still discover, create, and select development environments without errors.

Quick Start

Run all end-to-end tests using the command npm run compile && npm run compile-tests && npm run e2e-test.

Frequently Asked Questions about run-e2e-tests

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

FAQPage Schema
How do I run end-to-end tests to validate user workflows in a VS Code extension?

End-to-end tests for VS Code extensions validate complete user workflows like environment discovery, creation, and selection. They test the entire user journey to catch integration issues that isolated unit or smoke tests might miss.

What do I need to execute e2e tests for VS Code extension development environments?

Running e2e tests with npm validates full system integration and ensures critical paths work correctly before releases. This pre-release assurance catches workflow regressions in environment discovery and execution that unit tests miss.

How do I run end-to-end tests to validate user workflows in a VS Code extension?

End-to-end testing in VS Code extensions handles scenarios like environment discovery, creation, selection, and execution. It ensures these complete user workflows function correctly together, preventing regressions before deploying a new version.

Why use end-to-end tests instead of unit tests for VS Code extension release validation?

Skills for unit testing validate isolated components within a VS Code extension, producing individual module pass or fail results to catch localized logic errors before broader integration checks.

What scenarios do e2e tests cover for VS Code extension environment selection?

Skills for unit testing validate isolated components within a VS Code extension, producing individual module pass or fail results to catch localized logic errors before broader integration checks.