skills.rest
exceptionless
exceptionlessOFFICIAL
Explore all skills by this author →
Website𝕏@ExceptionlessGitHub

e2e-testing

Create and run Playwright end-to-end browser tests with Page Object Models.

2.5k|507|Updated Feb 7, 2014
Search Tags:#automation#accessibility#playwright#e2e testing#browser testing#page object model
One-click install
npx skills add https://github.com/exceptionless/Exceptionless --skill e2e-testing-exceptionless
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/exceptionless/Exceptionless/tree/main/.agents/skills/e2e-testing
Command: npx skills add https://github.com/exceptionless/Exceptionless --skill e2e-testing-exceptionless

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of writing, running, and debugging end-to-end browser tests, ensuring application quality and user flow integrity.

Core Features & Use Cases

  • Page Object Model: Implement reusable page interactions for maintainable tests.
  • Selector Strategies: Prioritize semantic selectors (getByRole, getByLabel) and test IDs for robust locators.
  • Accessibility Audits: Integrate axe-playwright for automated accessibility checks.
  • Use Case: When adding new user authentication features, use this skill to create Playwright tests that verify successful login, password reset flows, and error handling for invalid credentials, ensuring a smooth user experience.

Quick Start

Use the e2e-testing skill to run all end-to-end tests with the command npm run test:e2e.

Frequently Asked Questions about e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write maintainable Playwright E2E tests for user flows?▼

Maintainable Playwright E2E tests use the Page Object Model pattern to encapsulate reusable page interactions. This Skill helps structure locators and actions so complex user flows stay readable and easy to update as the application grows.

What is the best way to select elements in Playwright to avoid flaky browser tests?▼

Robust Playwright selectors prioritize semantic locators like getByRole and getByLabel, or fall back to test IDs. This approach targets elements by their accessible role rather than brittle CSS classes, reducing flaky browser tests during DOM changes.

Can I run automated accessibility audits alongside Playwright browser testing?▼

Yes, automated accessibility audits run alongside Playwright browser testing by integrating axe-playwright. This Skill validates user flows through the browser while simultaneously checking for accessibility compliance during the E2E test execution.

How do I run all end-to-end tests after adding new authentication features?▼

Run all end-to-end tests by executing the command `npm run test:e2e`. This Skill sets up the Playwright test runner to validate user authentication features, password reset flows, and error handling for invalid credentials.

Does this E2E testing approach require specific test runner dependencies?▼

No specific test runner dependencies are required to start writing and running E2E tests. This Skill facilitates Playwright test creation directly, supporting selector strategies and accessibility audits without external module dependencies.

Related Skills

Explore More Software Engineering Skills→
namninhndnamninhnd

Playwright Browser Automation

Automate web browser interactions with Playwright via MCP server or Node.js API.

Community
Advanced
Codagent-AICodagent-AI
30

wait-ci

Poll GitHub CI status and fetch failed run logs for pull requests.

Official
Advanced
calexandarcalexandar

pest-testing

Execute Pest-based tests across unit, feature, and browser contexts in Laravel or PHP projects.

Community
Intermediate
williamzujkowskiwilliamzujkowski
17

e2e-testing

Automate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.

Community
Intermediate