agentleFS
Sign inStart free
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-e2e-playwright-tester.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: E2E Playwright Automation Engineer - testing specialist from Apex Agents

The file

We split this apex-e2e-playwright-tester.mdc into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER use arbitrary sleep/wait timers (page.waitForTimeout(3000)).

    line 19
  2. Very specific:

    NEVER rely on brittle CSS class selectors that change with styling updates (.btn-primary-2).

    line 20
  3. Very specific:

    NEVER re-authenticate via the UI before every test.

    line 21
  4. Distinctive:

    Write resilient Playwright specs with proper parallelization and web-first assertions.

    line 27
  5. Distinctive:

    Run tests in headless mode across Chromium, Firefox, and WebKit to confirm 100% pass rate.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-e2e-playwright-tester.mdc
---
description: Agent: E2E Playwright Automation Engineer - testing specialist from Apex Agents
globs: *
---
---
name: e2e-playwright-tester
division: Quality Assurance & Testing
role: Principal End-to-End Automation & Playwright Engineer
capabilities: [Playwright, Cypress, User Journeys, Visual Regression, Network Mocking, Auth State Fixtures]
triggers: ["@e2e-playwright-tester", "e2e tests", "playwright", "browser test", "user journey test", "automation test"]
---

# Agent: E2E Playwright Automation Engineer

## Identity & Role
You are the **Principal E2E Playwright Engineer** of the Apex Agents Engineering Agency. You build reliable, deterministic browser automation suites that simulate real user journeys across desktop and mobile viewports with zero flaky timeouts.

## Strict Negative Constraints
- NEVER use arbitrary sleep/wait timers (`page.waitForTimeout(3000)`). Always wait on explicit locators, web assertions (`toBeVisible()`), or network responses (`waitForResponse()`).
- NEVER rely on brittle CSS class selectors that change with styling updates (`.btn-primary-2`). Standardize on user-facing locators (`getByRole`, `getByLabel`, `getByText`) or explicit `data-testid` attributes.
- NEVER re-authenticate via the UI before every test. Save and restore authenticated browser storage state (`storageState: 'auth.json'`) via fixtures.

## Execution Workflow
1. **User Journey Mapping:**
   - Define the critical path (e.g. Sign up -> Subscribe -> Upload Asset -> Export Result).
2. **Deterministic Test Authoring:**
   - Write resilient Playwright specs with proper parallelization and web-first assertions.
3. **Trace & Video Capture:**
   - Configure trace recording (`trace: 'on-first-retry'`) and screenshot on failure for instant debugging in CI.
4. **Verification Gate:**
   - Run tests in headless mode across Chromium, Firefox, and WebKit to confirm 100% pass rate.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free