e2e-tester

e2e-tester is a cursor rule for Cursor from GktuOktay/ai-skills. It costs 0 tokens per session (1,102 once invoked), scanned A, original, MIT.

A guide for end-to-end testing, which checks complete user journeys through an application rather than testing isolated pieces of code. It covers tools such as Cypress, Playwright, and Appium.

In plain words
What is it for?
Use it to test important flows such as submitting forms, logging in, or completing actions across a web or mobile application.
Why use it?
It helps reveal failures that occur when the interface, application logic, and connected services must work together.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to test important flows such as submitting forms, logging in, or completing actions across a web or mobile application.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/gktuoktay/ai-skills/e2e-tester
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/GktuOktay/ai-skills

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for e2e-tester

README.md
[![agentmods](https://agentmods.dev/badge/rules/gktuoktay/ai-skills/e2e-tester/github.svg)](https://agentmods.dev/rules/gktuoktay/ai-skills/e2e-tester)
Your own site
<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/e2e-tester"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/e2e-tester/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for e2e-tester

Your own site · 80×15
<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/e2e-tester"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/e2e-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01102
Opus 5 $0.00000 $0.00551
Sonnet 5 $0.00000 $0.00220
Haiku 4.5 $0.00000 $0.00110

Measured 6d ago against content hash 6a5a1c7ea0ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

e2e-tester scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/cursor/rules/e2e-tester.mdc · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

E2E Tester Guidelines

As an E2E (End-to-End) Tester, you validate complete user journeys across the entire application stack. You simulate real user interactions using tools like Playwright, Cypress, or Appium to ensure that all integrated components function seamlessly together.

Core Philosophy

  1. User-Centric: Test flows exactly as a user would experience them.
  2. Resilience: Tests should be robust against minor UI changes and network delays.
  3. Scope: Focus on critical business flows; do not duplicate exhaustive unit tests.
  4. Environment: Run tests in an environment that closely mirrors production.

DOM Querying Strategies

Selecting elements reliably is crucial for preventing flaky tests.

Strategy Priority Description Example
Accessibility Roles Highest Queries based on accessibility attributes (ARIA). getByRole('button', { name: 'Submit' })
Data Attributes High Using dedicated attributes like data-testid. getByTestId('submit-btn')
Text Content Medium Querying by visible text on the page. getByText('Welcome back!')
CSS Selectors Low Querying by classes or IDs (prone to breaking). .btn-primary or #submit
XPath Lowest Fragile structure-based queries. Avoid if possible. //div[1]/span/button

Best Practice: Advocate for data-testid attributes or proper ARIA roles in the application code.

User Journey Definitions

Structure your tests around complete, valuable user journeys.

// Playwright Example: User Checkout Journey
import { test, expect } from '@playwright/test';

test.describe('E-Commerce Checkout Journey', () => {
  test('User can successfully add item to cart and checkout', async ({ page }) => {
    // 1. Navigate and Search
    await page.goto('https://shop.example.com');
    await page.getByPlaceholder('Search products').fill('Wireless Headphones');
    await page.keyboard.press('Enter');

    // 2. Select and Add to Cart
    await page.getByRole('link', { name: 'Noise Cancelling Headphones X1' }).click();
    await page.getByRole('button', { name: 'Add to Cart' }).click();
    await expect(page.getByText('1 item in cart')).toBeVisible();

    // 3. Checkout
    await page.getByRole('button', { name: 'Proceed to Checkout' }).click();
    
    // ... Fill forms using semantic queries ...
    
    // 4. Verify Success
    await expect(page.getByRole('heading', { name: 'Order Confirmed' })).toBeVisible();
  });
});

Read the full file on GitHub · 107 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 107 lines · 1,102 tokens per session scan A 6a5a1c7ea0ed

Subscribe to this mod's changes

e2e-tester is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,102 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.