Execute end-to-end tests covering full user workflows across frontend and backend.

MITAuto-check passedTesting & QA

Install Running E2E Tests

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-e2e-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace running-e2e-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/running-e2e-tests .claude/skills/running-e2e-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
running-e2e-tests
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
513 words
Files
4 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Execute end-to-end tests covering full user workflows across frontend and backend.

  • Works in 7 steps: Identify critical user journeys to cover → Create page object models (POM) for… → Write E2E test files organized by user… → …
  • Performing specialized testing
  • SKILL.md covers Current State, Overview, Prerequisites and Instructions, plus 4 more sections
  • Calls npx

What it does

Running E2E Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute end-to-end tests covering full user workflows across frontend and backend. Use when performing specialized testing. Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA, covering End-to-end testing and UX design. It works with Selenium, Playwright and Cypress. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Performing specialized testing
  • With phrases like run end-to-end tests
  • Test user flows
  • Execute E2E suite

Example prompts

  • “run end-to-end tests”
  • “test user flows”
  • “execute E2E suite”
  • “/running-e2e-tests”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:e2e-*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Identify critical user journeys to cover
  2. Create page object models (POM) for reusable page interactions
  3. Write E2E test files organized by user journey
  4. Handle authentication efficiently
  5. Configure multi-browser and responsive testing
  6. Add retry and stability mechanisms
  7. Generate test reports with screenshots, traces, and video on failure.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(test:e2e-*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • playwright.dev
    • docs.cypress.io
    • martinfowler.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Running E2E Tests loads about 1.5k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 513 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 513 words, ~1,490 tokens.

Download SKILL.mdSave it as .claude/skills/running-e2e-tests/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
running-e2e-tests
description
Execute end-to-end tests covering full user workflows across frontend and backend. Use when performing specialized testing. Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(test:e2e-*)
compatibility
Designed for Claude Code
version
1.21.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
testing, workflow, e2e-tests

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.
    • Use Playwright projects to define browser/viewport combinations.
  6. Add retry and stability mechanisms:
    • Use expect with auto-waiting locators (Playwright) instead of explicit waits.
    • Configure test retries (max 2) for CI environments.
    • Add networkidle or domcontentloaded wait conditions for page transitions.
  7. Generate test reports with screenshots, traces, and video on failure.
Show full SKILL.md (197 more words)Show less

Output

  • E2E test files organized by user journey in tests/e2e/ or e2e/
  • Page object model classes in tests/e2e/pages/
  • Playwright/Cypress configuration file with browser and viewport matrix
  • Authentication state file for session reuse
  • HTML test report with screenshots, traces, and failure details

Error Handling

ErrorCauseSolution
Element not found / timeoutSelector changed or element lazy-loaded after timeoutUse data-testid attributes; increase timeout; use waitFor with proper state checks
Test passes locally but fails in CIHeadless browser behavior differs or CI is slowerRun CI in headless mode locally to reproduce; increase timeouts; check viewport size
Authentication state expiredStored session tokens have short TTLRegenerate auth state before each test run; use long-lived test account tokens
Flaky test due to animationClick registered before animation completesDisable CSS animations in test config; use force: true on click; add waitForLoadState
Database state pollutionPrevious test left data that affects current testSeed database in beforeEach; use transactional rollback; reset via API endpoint

Examples

Playwright test for user registration flow:

typescript
import { test, expect } from '@playwright/test';

test('new user can register and see dashboard', async ({ page }) => {
  await page.goto('/register');
  await page.getByTestId('name-input').fill('Test User');
  await page.getByTestId('email-input').fill('test@example.com');
  await page.getByTestId('password-input').fill('SecurePass123!');
  await page.getByTestId('register-button').click();

  await expect(page).toHaveURL(/\/dashboard/);
  await expect(page.getByTestId('welcome-message')).toContainText('Test User');
});

Page object model:

typescript
export class LoginPage {
  constructor(private page: Page) {}
  async login(email: string, password: string) {
    await this.page.goto('/login');
    await this.page.getByTestId('email').fill(email);
    await this.page.getByTestId('password').fill(password);
    await this.page.getByTestId('submit').click();
    await this.page.waitForURL(/\/dashboard/);
  }
}

Playwright config with multi-browser projects:

typescript
export default defineConfig({
  projects: [
    { name: 'chromium', use: { ...devices['Desktop Chrome'] } },
    { name: 'firefox', use: { ...devices['Desktop Firefox'] } },
    { name: 'mobile', use: { ...devices['iPhone 14'] } },
  ],
  use: { screenshot: 'only-on-failure', trace: 'on-first-retry' },
});

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references, assets) in skills/.curated/running-e2e-tests of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Running E2E Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Running E2E Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Running E2E Tests this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: PassMIT
Open BrowserJasonHonKL/Openbrowser114—~1.6kAutomated safety check: PassMIT
Migratealirezarezvani/claude-skills28k1 repos~1kAutomated safety check: PassMIT
Playwright Proalirezarezvani/claude-skills28k1 repos~1.4kAutomated safety check: PassMIT
Playwright Migrationzebbern/claude-code-guide4.7k2 repos~187Automated safety check: PassMIT
Cypress Automationpetrkindlmann/qa-skills168—~4.4kAutomated safety check: PassMIT

Similar skills

  • Open Browser

    JasonHonKL/Openbrowser

    A skill your agent uses whenever the task involves browsing web pages, extracting page content, clicking forms, or completing web workflows.

    114 GitHub stars~1.6k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Migrate

    alirezarezvani/claude-skills

    Migrate from Cypress or Selenium to Playwright. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~1k tokens
    Testing & QAAuto-check passed
  • Playwright Pro

    alirezarezvani/claude-skills

    Production-grade Playwright testing toolkit. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~1.4k tokens
    Testing & QAAuto-check passed
  • Playwright Migration

    zebbern/claude-code-guide

    Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.

    4.7k GitHub starsUsed in 2 repos~187 tokens
    Testing & QAAuto-check passed
  • Cypress Automation

    petrkindlmann/qa-skills

    Build Cypress test suites in TypeScript: E2E tests, component tests, custom commands, cy.intercept network control, cy.session login, Cypress Cloud, and CI integration.

    168 GitHub stars~4.4k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Test Framework Migration Skill

    sickn33/agentic-awesome-skills

    Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.

    47k GitHub starsUsed in 1 repo~2.2k tokens
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Running E2E Tests

What does Running E2E Tests do?

Execute end-to-end tests covering full user workflows across frontend and backend. Running E2E Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute end-to-end tests covering full user workflows across frontend and backend.

When should I use Running E2E Tests?

Running E2E Tests fits situations like: performing specialized testing; with phrases like run end-to-end tests; test user flows; execute E2E suite.

How do I install Running E2E Tests in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-e2e-tests -a claude-code`. Or copy the skill folder (skills/.curated/running-e2e-tests in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/running-e2e-tests in your project. Claude Code loads it when a task matches its description.

How do I install Running E2E Tests in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-e2e-tests -a codex`. Or copy the skill folder (skills/.curated/running-e2e-tests in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/running-e2e-tests in your project. Codex loads it when a task matches its description.

Can I use Running E2E Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-e2e-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/running-e2e-tests, .gemini/skills/running-e2e-tests, .github/skills/running-e2e-tests and .opencode/skills/running-e2e-tests in your project.

What does Running E2E Tests need to run?

Going by SKILL.md and its folder, Running E2E Tests needs the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(test:e2e-*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Running E2E Tests access the network?

SKILL.md names 3 domains. As links in the text: playwright.dev, docs.cypress.io and martinfowler.com. This is read from the text; nothing was executed.

Is Running E2E Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Running E2E Tests use?

Running E2E Tests is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Running E2E Tests use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16 tokens, read only when the agent opens those files.

What are the alternatives to Running E2E Tests?

Skills that share tags, products or a category with Running E2E Tests: Open Browser (JasonHonKL/Openbrowser, 114 stars), Migrate (alirezarezvani/claude-skills, 28k stars), Playwright Pro (alirezarezvani/claude-skills, 28k stars) and Playwright Migration (zebbern/claude-code-guide, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Running E2E Tests?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.