A guide for browser-level tests of the real Angular application using Playwright, a tool that controls browsers during tests. E2E tests check complete user journeys across the interface and backend.

It helps test authentication and feature flows, browser journeys, visual screenshots, and accessibility, using the repository's configured test commands.

It standardises where tests, reusable setup, generated clients, screenshots, and accessibility checks go, and avoids using an unsupported Playwright installation.

uitesting — Cursor rule for Cursor by theimaginaryfoundation

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/theimaginaryfoundation/what-iff

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/theimaginaryfoundation/what-iff/uitesting/github.svg)](https://agentmods.dev/rules/theimaginaryfoundation/what-iff/uitesting)

Your own site

<a href="https://agentmods.dev/rules/theimaginaryfoundation/what-iff/uitesting"><img src="https://agentmods.dev/badge/rules/theimaginaryfoundation/what-iff/uitesting/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/theimaginaryfoundation/what-iff/uitesting"><img src="https://agentmods.dev/badge/rules/theimaginaryfoundation/what-iff/uitesting.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,234 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01234
Opus 5	$0.00000	$0.00617
Sonnet 5	$0.00000	$0.00247
Haiku 4.5	$0.00000	$0.00123

Measured yesterday against content hash 5197d8719569, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

uitesting 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 yesterday.

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.

.cursor/rules/uitesting.mdc · 113 lines

How it starts

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

Frontend E2E (Playwright)

Browser-level tests against the real Angular app, in web/app/e2e. Full detail lives in web/app/e2e/README.md — this rule is a summary, not a duplicate. All commands run via the repo's @playwright/test devDependency (npx playwright / the npm scripts) — never a separately pinned or global Playwright install.

Layout

e2e/
  poms/       # Page Object Models — locators + interactions only, no assertions, no env awareness
  fixtures/   # test.extend fixtures (testUser, userWithPersonality, seed, apiClient); api.ts holds raw HTTP calls
  sdk/        # openapi-typescript-generated client (npm run sdk:generate)
  tests/
    functional/   # per-feature specs: auth/, personality/, profile/
    journeys/     # cross-cutting flows
    visual/       # toHaveScreenshot specs + committed __screenshots__ baselines
    a11y/         # axe-core scans
  scripts/
    visual-docker.sh   # runs tests/visual inside the Playwright Docker image
  playwright.config.base.ts   # shared settings + the three browser projects
  playwright.config.{mock-llm,local-llm}.ts

Which config

The config/backend/tag matrix lives in one place: web/app/e2e/README.md ("Configs"), with the reasoning in e2e/docs/what-runs-where.md. Read it there — do not restate it here.

This section used to carry its own copy of that table and it drifted, which is the argument for the rule: it listed a retired @no-prod tag no config honours, omitted tags configs actually exclude, and gave wrong guidance on E2E_BASE_URL / E2E_API_BASE_URL. Anyone following it would have set variables that override the correct values.

The one thing worth stating here because it is not in the table: there is no root playwright.config.ts — always pass --config (the npm scripts do).

Backend prerequisites

Local configs only start the Angular dev server, not the backend:

make db-up
make dev-up   # or: make run-mock / make run-local

Writing tests

POMs (e2e/poms/): locators + interactions only, no assertions, no env awareness. Grow an existing POM rather than putting a raw locator in a spec.
Locate by aria-label, role, or placeholder — the app has no data-testid attributes.
Use the shared fixtures from e2e/fixtures/index.ts (testUser, userWithPersonality, seed, apiClient) instead of bare @playwright/test.
e2e/fixtures/api.ts is the only file allowed to hand-roll HTTP; new endpoint calls should go through e2e/sdk/ (regenerate with npm run sdk:generate after an openapi.yaml change).
Run npm run lint:e2e before considering e2e work done.

Read the full file on GitHub · 113 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.

yesterday First seen · 113 lines · 0 tokens per session scan A 5197d8719569

Subscribe to this mod's changes

uitesting is a cursor rule published in the GitHub repository theimaginaryfoundation/what-iff (15 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,234 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-09.

E2E testing Testing

maestro-device-selection

Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.

duckduckgo/apple-browsers · 0 tokens

puppeteer

This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.

sanjeed5/awesome-cursor-rules-mdc · 1,826 tokens

uitesting