| 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
| Action | Command |
|---|
| Run all E2E tests | npm run compile && npm run compile-tests && npm run e2e-test |
| Run specific test | npm run e2e-test -- --grep "discovers" |
| Debug in VS Code | Debug panel → "E2E Tests" → F5 |
How E2E Tests Work
Unlike unit tests (mocked) and smoke tests (quick checks), E2E tests:
- Launch a real VS Code instance with the extension
- Exercise complete user workflows via the real API
- Verify end-to-end behavior (discovery → selection → execution)
They take longer (1-3 minutes) but catch integration issues.
Workflow
Step 1: Compile and Run
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)
