Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计通过

running-e2e-tests运行端到端测试

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

685

周安装

28

GitHub Stars

2,083

下载量

220
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:running-e2e-tests(运行端到端测试)
来源仓库:https://github.com/jeremylongshore/claude-code-plugins-plus-skills
仓库路径:skills/running-e2e-tests
安装命令:
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-e2e-tests
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-e2e-tests

简介

用于辅助测试设计、自动化测试、用例整理和回归验证。

  • 适合编写单元测试、端到端测试或根据失败日志定位问题。
  • 需确认项目测试框架、运行命令和夹具数据后使用。
  • 涉及浏览器或外部服务时,应区分本地模拟与生产环境。
  • running-e2e-tests 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

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).

  1. 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.

  1. 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.

  1. 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.

  1. 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.

  1. 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.

  1. Generate test reports with screenshots, traces, and video on failure.

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:

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:

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:

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.61%
按下载量换算76

Claude

31.05%
按下载量换算68

Cursor

20.41%
按下载量换算45

Gemini CLI

10.9%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills