E

Skill 详情

e2e-testing

End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.

来源平台:GitHub
来源标识:sickn33/antigravity-awesome-skills
源文件:原始说明
自动化与浏览器 超热门 GitHub 低 风险 下载 2.02万Stars 3.68万 GitHub Copilot
来源平台GitHub
文档版本SKILL.md
热度超热门
排名信号下载 2.02万
概述 安装 文档 下载

快速判断

End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.

最后校验2026-05-27
来源平台GitHub
安全提示
下载副本ZIP 可用

适合任务

  • 把重复任务整理成可复用的 AI 操作流程。
  • 让 AI 在特定场景下按统一规范执行。
  • 为团队或个人工作流提供可复制的任务说明。

输入与输出

输入:任务目标、上下文材料、文件路径、约束条件或需要处理的内容。

输出:按 Skill 说明生成的文档、代码、检查结果、计划、建议或操作步骤。

示例任务

  • 使用 e2e-testing 帮我处理当前任务,并说明执行前需要确认的输入。
  • 根据 e2e-testing 的说明,给我一个安全的使用步骤清单。

安装方式

  1. 下载本站提供的 Skill ZIP 并解压。
  2. 把解压后的 Skill 目录放入当前 AI 工具支持的 skills 目录。
  3. 如需在线查看原始内容,可打开 GitHub 的 SKILL.md

在线原始地址:e2e-testing/SKILL.md

风险边界

使用前请检查权限、外部依赖和要处理的数据类型。不要把密码、密钥、身份信息或敏感客户资料交给未经确认的 Skill。

SKILL.md 文档介绍

E2E Testing Workflow

Overview

Specialized workflow for end-to-end testing using Playwright including browser automation, visual regression testing, cross-browser testing, and CI/CD integration.

When to Use This Workflow

Use this workflow when:

  • Setting up E2E testing
  • Automating browser tests
  • Implementing visual regression
  • Testing across browsers
  • Integrating tests with CI/CD

Workflow Phases

Phase 1: Test Setup

Skills to Invoke

  • playwright-skill - Playwright setup
  • e2e-testing-patterns - E2E patterns

Actions

1. Install Playwright

2. Configure test framework

3. Set up test directory

4. Configure browsers

5. Create base test setup

Copy-Paste Prompts

Use @playwright-skill to set up Playwright testing

Phase 2: Test Design

Skills to Invoke

  • e2e-testing-patterns - Test patterns
  • test-automator - Test automation

Actions

1. Identify critical flows

2. Design test scenarios

3. Plan test data

4. Create page objects

5. Set up fixtures

Copy-Paste Prompts

Use @e2e-testing-patterns to design E2E test strategy

Phase 3: Test Implementation

Skills to Invoke

  • playwright-skill - Playwright tests
  • webapp-testing - Web app testing

Actions

1. Write test scripts

2. Add assertions

3. Implement waits

4. Handle dynamic content

5. Add error handling

Copy-Paste Prompts

Use @playwright-skill to write E2E test scripts

Phase 4: Browser Automation

Skills to Invoke

  • browser-automation - Browser automation
  • playwright-skill - Playwright features

Actions

1. Configure headless mode

2. Set up screenshots

3. Implement video recording

4. Add trace collection

5. Configure mobile emulation

Copy-Paste Prompts

Use @browser-automation to automate browser interactions

Phase 5: Visual Regression

Skills to Invoke

  • playwright-skill - Visual testing
  • ui-visual-validator - Visual validation

Actions

1. Set up visual testing

2. Create baseline images

3. Add visual assertions

4. Configure thresholds

5. Review differences

Copy-Paste Prompts

Use @playwright-skill to implement visual regression testing

Phase 6: Cross-Browser Testing

Skills to Invoke

  • playwright-skill - Multi-browser
  • webapp-testing - Browser testing

Actions

1. Configure Chromium

2. Add Firefox tests

3. Add WebKit tests

4. Test mobile browsers

5. Compare results

Copy-Paste Prompts

Use @playwright-skill to run cross-browser tests

Phase 7: CI/CD Integration

Skills to Invoke

  • github-actions-templates - GitHub Actions
  • cicd-automation-workflow-automate - CI/CD

Actions

1. Create CI workflow

2. Configure parallel execution

3. Set up artifacts

4. Add reporting

5. Configure notifications

Copy-Paste Prompts

Use @github-actions-templates to integrate E2E tests with CI

Quality Gates

  • [ ] Tests passing
  • [ ] Coverage adequate
  • [ ] Visual tests stable
  • [ ] Cross-browser verified
  • [ ] CI integration working

Related Workflow Bundles

  • testing-qa - Testing workflow
  • development - Development
  • web-performance-optimization - Performance

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
建议反馈