Stats
Actions
Tags
From devkit
E2E Chrome DevTools MCP を使って E2E テストを実行する。docs/e2e-testing/RUNBOOK.md のランブックを読み込んで実行。
How this command is triggered — by the user, by Claude, or both
Slash command
/devkit:e2e-chrome-devtools-mcpThe summary Claude sees in its command listing — used to decide when to auto-load this command
docs/e2e-testing/RUNBOOK.md を読み込んでその中身を実行する
docs/e2e-testing/RUNBOOK.md を読み込んでその中身を実行する
npx claudepluginhub sumik5/sumik-llm-plugin --plugin devkit/browser-testRun browser-based regression tests against spec files in docs/specs/. Verifies acceptance criteria in a running app via Chrome MCP, produces pass/fail reports with screenshots.
/testLaunches Chrome for manual UI testing at given URL, monitors console errors during interaction, generates report with screenshots and logs on completion.
/testRuns comprehensive E2E tests with Playwright on all pages, roles, and flows from test plan at <base-url>, optionally filtering roles/viewport/headless.
/candid-chrome-qaDrives real Chrome sessions against a running web app on desktop/mobile viewports, probes DOM/console/network for bugs, outputs structured JSON findings to .context/findings/.
/playwright-testGenerates Playwright E2E test specs from user flows, executes tests with traces, analyzes failures via screenshots, and implements fixes.
/run-e2eRuns end-to-end tests using Playwright, Cypress, or Selenium; auto-detects framework, starts server if needed, filters by optional test pattern, and outputs summary table with pass/fail counts, failure details, and fix suggestions.