Agent skill · software engineering · jeremylongshore
running-e2e-tests
Execute end-to-end tests covering full user workflows across frontend
Why this skill is useful
Adds specific commands and patterns for executing end-to-end tests with Playwright, Cypress, and Selenium that the AI wouldn't reliably generate on its own.
What it needs
Requires cypress, playwright, selenium installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
E2E Test Framework Current State !cat package.json 2>/dev/null grep -oE 'playwright cypress selenium' echo 'No E2E framework detected' Overview Execute end-to-end tests that simulate real user workflows across the full application stack -- browser interactions, API calls, database operations, and third-party integrations. Supports Playwright (recommended), Cypress, Selenium, and Puppeteer. Prerequisites E2E testing framework installed (Playwright, Cypress, or Selenium WebDriver) Application running in a test environment with seeded test data Browser binaries installed (npx playwright install or Cypress binary) Test user accounts created with known credentials Environment variables configured for base URL, API keys, and test credentials Instructions 1. Identify critical user journeys to cover: User registration and login flow. Primary feature workflow (e.g., create item, edit, delete). Search and filtering functionality. Checkout or payment flow (if applicable). Error handling (404 pages, form validation, session expiry). 2. Create page object models (POM) for reusable page interactions: One class per page or major component. Encapsulate locators, actions (click, fill, select), and assertions. Use data-testid attributes as primary selectors for stability. 3. Write E2E test files organized by user journey: Each test file covers one complete workflow. Use beforeEach to navigate to the starting page and reset state. Use afterEach to capture screenshots on failure. Keep tests independent -- no test should depend on another test's output. 4. Handle authentication efficiently: Store authenticated session state to a file (storageState in Playwright). Reuse session across tests that require login. Create a separate auth setup fixture that runs once per worker. 5. Configure multi-browser and responsive testing: Run tests on Chromium, Firefox, and WebKit. Test at mobile (375px), tablet (768px), and desktop (1280px) viewports. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/running-e2e-tests--ac3b21