e2e-testing

Plugin e2e-testing from marketplace shahjalal-plugins in shahjalalgit/ai-agents. Commands read from the repo's manifest — 5 days ago.

Skills (5)

• e2e-evidence

  Record, collect and publish Playwright E2E evidence (results table per acceptance criterion, named screenshots, videos, traces, and the criteria that were tested) as one sticky comment on a GitHub issue. Use after the spec passes or reproduces the bug, or when asked to post test evidence.

• from-issue

  Write and run Playwright E2E tests for a GitHub issue, then post the evidence on the issue. Checks the issue is clear enough to test and asks the user (or the issue author) when it is not, plans against the live app, generates and heals the spec, proves it is stable, and posts a results comment with

• issue-readiness

  Definition of Ready for turning a GitHub issue into E2E tests: how to find existing acceptance criteria or test cases and use them verbatim, how to derive criteria from the issue and its PR diff when none exist, the six fields every criterion needs, and how to phrase clarifying questions. Use when j

• playwright-best-practices

  Rules for reliable, maintainable Playwright E2E tests: locator priority, web-first waiting, test isolation, structure with ACn titles and Given/When/Then steps, mocking boundaries, bug reproduction with test.fail(), and evidence screenshots. Use whenever writing, reviewing or fixing Playwright tests

• setup

  One-time setup of a project for issue-driven Playwright E2E testing: checks Playwright 1.56+, adds a seed test, the evidence config, GitHub issue forms with acceptance-criteria fields, and .gitignore entries. Use when /e2e-testing:from-issue reports missing setup, or when asked to set up e2e testing

Subagents (4)

• e2e-generator

  Turns an issue's Playwright test plan into a runnable spec file that follows the project's own conventions (fixtures, page objects, helpers), verifying every locator and assertion live with Playwright's test MCP tools. Use after e2e-planner has saved a plan.

• e2e-healer

  Runs an issue's Playwright spec, diagnoses each failure from traces and error context, fixes test bugs (locators, waits, data) without hiding app bugs, marks confirmed bugs in reproduce mode, and proves the spec is stable with repeated runs. Use after e2e-generator, or when an issue's E2E spec fails

• e2e-planner

  Explores the live app with Playwright's test MCP tools and turns an issue's agreed acceptance criteria file into a Markdown Playwright test plan (one scenario per AC). Reports where the UI contradicts the issue. Use after the clarity gate, before generating tests.

• issue-analyst

  Reads a GitHub issue (body, comments, linked PRs and diff) and returns a readiness report for E2E testing: the acceptance criteria (taken verbatim from the issue, or derived from the details and the PR diff when it has none), the target environment, the mode (verify or reproduce), gaps, and the exac

MCP servers (1)

• playwright-test

  runs: npx --no-install playwright run-test-mcp-server --headless -c ${CLAUDE_PROJECT_DIR}/${user_config.playwright_config}

Similar plugins