e2e-tester
e2e-tester equips you with patterns and practices for writing robust Playwright end-to-end tests organized through the Page Object Model approach. Learn how to structure test suites that remain maintainable as your application grows, separating test logic from UI interactions for cleaner, more reliable automation.
e2e-tester teaches you to write end-to-end tests by leveraging the Page Object Model pattern, which separates test logic from UI interactions. Start by creating page objects that encapsulate selectors and actions for each page or component, then write test cases that call these reusable methods. This approach keeps your tests maintainable and readable as your application grows, and e2e-tester guides you through structuring test suites with proper file organization so that tests remain reliable and easy to update when your UI changes.
AI-generated summary based on this skill's SKILL.md
Install
PageAI-Pro/ralph-loop/e2e-tester · repository language: Shell
git clone https://github.com/PageAI-Pro/ralph-loop
cp -r ralph-loop/.agent/skills/e2e-tester ~/.claude/skills/e2e-testerFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write end to end tests using e2e-tester and Playwright?
e2e-tester teaches you to write end-to-end tests by leveraging the Page Object Model pattern, which separates test logic from UI interactions. Start by creating page objects that encapsulate selectors and actions for each page or component, then write test cases that call these reusable methods. This approach keeps your tests maintainable and readable as your application grows, and e2e-tester guides you through structuring test suites with proper file organization so that tests remain reliable and easy to update when your UI changes.
What is the page object model pattern in e2e-tester for Playwright?
e2e-tester emphasizes the Page Object Model (POM) as a core pattern for organizing Playwright tests. In POM, you create a class or module for each page or component that contains all the selectors and methods needed to interact with that page. Your actual test files then use these page objects rather than scattering selectors throughout your test code. This separation makes tests cleaner, more maintainable, and easier to refactor—when a UI element moves, you update only the page object, not dozens of test cases.
How does e2e-tester help with reliable selectors and waiting strategies in Playwright?
e2e-tester covers best practices for both selector choice and waiting strategies to ensure your Playwright tests are robust. It recommends using semantic selectors like getByRole whenever possible, as these are more resilient to styling changes than CSS or XPath selectors. For waiting, e2e-tester teaches you to rely on Playwright's built-in auto-waiting and explicit wait strategies rather than hard sleeps, ensuring your tests wait for elements to be actionable before interacting with them. These practices reduce flakiness and make your tests more reliable across different environments.
How do I set up and organize Playwright test files with e2e-tester?
e2e-tester guides you through proper file organization and configuration for Playwright tests. You'll learn to structure your project with dedicated directories for page objects, test specs, and reusable components, keeping configuration centralized in your Playwright config file. e2e-tester emphasizes creating reusable fixtures and helper functions so that common setup, teardown, and utility logic is shared across tests. This organization makes your test suite scalable and ensures that new tests can be added quickly without duplicating code or logic.
What debugging and optimization tools does e2e-tester recommend for Playwright tests?
e2e-tester introduces you to Playwright's debugging and optimization capabilities, including MCP exploration for interactive test development, trace files for detailed test execution playback, and visual regression testing to catch unintended UI changes. These tools help you identify flaky tests, understand test failures, and verify that your application's visual appearance remains consistent. By using traces and visual regression, e2e-tester helps you optimize your test suite and catch bugs that might otherwise slip through.
Can e2e-tester help integrate Playwright tests into CI/CD pipelines?
e2e-tester covers integration of Playwright tests into CI/CD pipelines with guidance on proper reporting and artifact handling. You'll learn how to configure Playwright to run in headless mode, generate test reports, and capture artifacts like screenshots and videos when tests fail. e2e-tester shows you how to set up your pipeline so that test results are visible to your team, failures are easy to diagnose, and your test suite runs reliably in automated environments alongside your deployment process.
SKILL.md
rendered from the published skill — quoted content, verbatim
Before you start: - check if any existing tests cover the functionality you are testing - check if a unit tests can cover the feature better - analyze if a end to end test brings any value over a unit test
If the answer is yes to any of the above, proceed with the end to end test creation.
MCP Workflow (MANDATORY If Available)
⚠️ If you have Playwright MCP tools, ALWAYS use them BEFORE creating any test:
- Navigate to target page
- Take snapshot to see page structure and elements
- Interact with forms/elements to verify exact user flow
- Take screenshots to document expected states
- Verify page transitions through complete flow (loading, success, error)
- Document actual selectors from snapshots (use real refs and labels)
- Only after exploring create test code with verified selectors
**If MCP NOT
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agent/skills/e2e-tester/SKILL.md