e2e-testing
Automate End-to-End Testing with Playwright
Manual testing is slow and error-prone. This skill provides a structured 7-phase workflow for automated E2E testing with Playwright, from setup to CI/CD integration.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「e2e-testing」。 Set up E2E testing for a React application
預期結果:
Creates Playwright configuration file, installs dependencies, sets up test directory structure, and provides example test file with login flow test
正在使用「e2e-testing」。 Run cross-browser tests
預期結果:
Executes test suite against Chromium, Firefox, and WebKit browsers with detailed pass/fail reports and screenshot artifacts for failed tests
安全審計
安全Static analyzer flagged 34 patterns (30 external_commands, 4 blocker) but all are false positives. The SKILL.md file is documentation, not executable code. Backticks are markdown formatting for skill references, not shell commands. No actual code execution or dangerous patterns exist.
品質評分
你能建構什麼
QA Engineers automating regression testing
Set up comprehensive E2E test suites that run automatically on every code change, catching regressions before production deployment.
Developers implementing test-driven development
Create automated browser tests alongside feature development to ensure user flows work correctly across all supported browsers.
DevOps teams building CI/CD pipelines
Integrate automated E2E testing into deployment workflows with parallel execution, artifacts, and test reporting.
試試這些提示
Use @playwright-skill to set up Playwright testing in my project. Install dependencies, configure test framework, and create a basic test file.
Use @e2e-testing-patterns to design an E2E test strategy for my application. Identify critical user flows that need automated testing.
Use @playwright-skill to implement visual regression testing. Set up baseline images and add visual assertions to detect UI changes.
Use @github-actions-templates to create a GitHub Actions workflow that runs E2E tests in parallel across browsers and uploads test artifacts.
最佳實務
- Use page object pattern to separate test logic from page structure for maintainable tests
- Implement proper wait strategies using Playwright auto-wait instead of hardcoded timeouts
- Run tests in headless mode for CI and headed mode locally for debugging
避免
- Using hardcoded sleep delays instead of Playwright's built-in auto-wait functionality
- Writing tests that depend on specific test execution order instead of isolated tests
- Storing test credentials in plain text instead of using environment variables