run-e2e
/run-e2e
Run Playwright E2E tests for the hosted MCP Cloudflare Worker. Use this skill when the user says /run-e2e, "run e2e tests", "run the e2e", "run playwright tests", or wants to test the hosted worker end-to-end. Handles starting Umbraco, building, and running the full test suite.
- Author
- umbraco ↗
- Repository
- Umbraco-MCP-Base ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run Playwright E2E tests for the hosted MCP Cloudflare Worker. Use this skill when the user says /run-e2e, "run e2e tests", "run the e2e", "run playwright tests", or wants to test the hosted worker end-to-end. Handles starting Umbraco, building, and running the full test suite.
Triggers from the description
Original author description
Run Playwright E2E tests for the hosted MCP Cloudflare Worker. Use this skill when the user says /run-e2e, "run e2e tests", "run the e2e", "run playwright tests", or wants to test the hosted worker end-to-end. Handles starting Umbraco, building, and running the full test suite.
How it works
- Steps
- Prerequisites reference
SKILL.md preview
---
name: run-e2e
description: Run Playwright E2E tests for the hosted MCP Cloudflare Worker. Use this skill when the user says /run-e2e, "run e2e tests", "run the e2e", "run playwright tests", or wants to test the hosted worker end-to-end. Handles starting Umbraco, building, and running the full test suite.
---
# Run E2E Tests
Playwright-based E2E tests that drive the MCP Inspector UI through the full OAuth flow against the real Forms worker (`src/worker.ts`), which includes both Forms tool collections and in-process CMS chaining.
Key files:
- Test file: `tests/forms-hosted-e2e/e2e/mcp-inspector.test.ts`
- Worker setup: `tests/forms-hosted-e2e/e2e/helpers/worker-setup.ts`
- Wrangler config: `tests/forms-hosted-e2e/wrangler.e2e.toml`
- Shared test helpers from `@umbraco-cms/mcp-hosted/testing`
## Steps
### 1. Check prerequisites
- Verify `demo-site/` exists (has a `.csproj` file). If not, tell the user to run `npx create-umbraco-mcp-server init`.
### 2. Kill stale processes
Kill any stale processes on the E2E ports (Umbraco, Worker, Inspector):
```bash
npm run kill:e2e-ports
```
Tell the user which stale processes were found and killed.
### 3. Build the project
Build the worker before running tests:
```bash
npm run build
```
### 4. Start Umbraco as a background subprocess
Start Umbraco using the existing npm script with `run_in_background: true`:
```bash
npm run start:umbraco
```
Then wait for Umbraco to be ready. Run this single bash command which loops until the health check succeeds (up to 120 seconds):
```bash
for i in $(seq 1 24); do if curl -sk -o /dev/null -w '%{http_code}' https://localhost:44374 --max-time 5 | grep -q '200\|302'; then echo "Umbraco is ready"; exit 0; fi; echo "Waiting for Umbraco... (attempt $i/24)"; sleep 5; done; echo "Umbraco failed to start within 120s"; exit 1
```
Tell the user you're waiting for Umbraco to start. If the health check fails after 120 seconds, tell the user and stop.
### 5. Run the E2E tests
The Cloudflare Worker and MCP Inspector are started automatically by the test framework (via `worker-setup.ts` and shared helpers) — no manual setup needed.
Run the tests:
```bash
npm run test:e2e
```
If the user asked for a specific test, use:
```bash
npx playwright test --config tests/forms-hosted-e2e/e2e/playwright.config.ts -g "<test-name>"
```
**Useful flags** the user may request:
- `--headed` — watch tests in browser
- `--debug` — open Playwright Inspector
- `SLOW_MO=500` — slow down browser actions
### 6. Report results
Show the test results to the user. If tests failed, read the relevant test file and any error output to help diagnose.
### 7. Cleanup
Do NOT stop the Umbraco instance after tests — the user may want to run them again or use it for other work. Only stop it if the user explicitly asks.
## Prerequisites reference
These must be set up once (not part of the skill flow):
1. **Umbraco demo-site** in `demo-site/` directory
2. **Umbraco backoffice user** with credentials: `admin@test.com` / `SecurePass1234`
3. **OAuth client** `umbraco-mcp-forms-hosted` registered in the Umbraco backoffice
4. **Playwright browsers**: `npx playwright install`
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · umbraco/Umbraco-MCP-Base | 100 | MIT |
| melodic-software/claude-code-plugins | 84 | MIT |
Database snapshot: 13.11.2026 · package version 4523079f3ffb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playwright-testing
UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing. - 95playwright-test
Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing,… - 100e2e-testing
Plans, generates, runs, and heals Playwright end-to-end tests through a spec-first loop with Playwright Test Agents and `@playwright/mcp`. Use when adding E2E coverage or hardening a flaky flow; triggers on "add e2e", "test this flow", "verify the user journey", "/e2e-testing". - 100playwright
Write, run, and maintain reliable end-to-end tests with Playwright. Use for test generation, CI integration, trace debugging, and cross-browser validation. - 95playwright-e2e-tests
Write and maintain Playwright end-to-end tests for the Onyx application. Use when creating new E2E tests, debugging test failures, adding test coverage, or when the user mentions Playwright, E2E tests, or browser testing. - 100playwright-test-writer
Write or extend Playwright end-to-end tests for a web page or feature. Use when the user asks to add, write, improve or fix Playwright, e2e or browser tests.