القائمة
Run Playwright E2E tests safely (warns about dev server conflicts)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | e2e |
| description | Run Playwright E2E tests safely (warns about dev server conflicts) |
| disable-model-invocation | true |
Run the Playwright end-to-end test suite for Tandem.
E2E tests will kill any running dev server. Playwright's webServer config starts its own servers on :3478/:3479, and freePort() kills existing processes on those ports. Do NOT run E2E tests while dev:server or dev:standalone is running unless you're OK losing that session.
Check for running dev servers and warn:
if curl -sf http://127.0.0.1:3479/health 2>/dev/null; then
echo "WARNING: Dev server detected on :3479. E2E tests will kill it."
echo "Stop your dev server first, or accept it will be terminated."
fi
Ask the user for confirmation if a server was detected.
Run the tests:
npm run test:e2e
For interactive debugging mode:
npm run test:e2e:ui
If tests fail, check:
data-testid attributes are present (kebab-case convention)openDocuments entries causing phantom tab removaldata-testid selectors (kebab-case): accept-btn, dismiss-btn, annotation-card-{id}tests/e2e/Cut a Tandem release — six-surface version bump, changelog, tag, GitHub Release publish, smoke checklist
Use when tandem_* MCP tools are available, the user asks about Tandem document editing, or iterating on text collaboratively. Provides workflow guidance, annotation strategy, and tool usage patterns for the Tandem collaborative editor.
Start Tandem dev environment (server + client) and verify MCP connection
Generate a Keep a Changelog entry from git log since the last tag
Capture README screenshots of the Tandem editor UI via Playwright + MCP
Debug Playwright E2E test failures — port conflicts, server startup, test isolation, and post-mortem analysis