playwright-testing

playwright-testing is a cursor rule for Cursor from kubev2v/forklift-console-plugin. It costs 10 tokens per session (2,333 once invoked), scanned A, original, Apache-2.0.

A workflow for browser-based end-to-end tests, which check complete user actions in a running interface. It covers upstream tests with mocked services and downstream tests with real provider connections.

In plain words
What is it for?
Use it to test the interface in a browser, write end-to-end tests, or check UI flows with mocked data or real providers.
Why use it?
It explains which test tier to use and how to run it, including when credentials and real infrastructure are required.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { setupForkliftIntercepts } from '../../intercepts';.

Good fit Use it to test the interface in a browser, write end-to-end tests, or check UI flows with mocked data or real providers.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin
agentmods
npx agentmods add rules/kubev2v/forklift-console-plugin/playwright-testing

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 playwright-testing

README.md
[![agentmods](https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/playwright-testing/github.svg)](https://agentmods.dev/rules/kubev2v/forklift-console-plugin/playwright-testing)
Your own site
<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/playwright-testing"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/playwright-testing/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 playwright-testing

Your own site · 80×15
<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/playwright-testing"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/playwright-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,333 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.00010 $0.02333
Opus 5.5 $0.00004 $0.00933
Sonnet 5.5 $0.00002 $0.00467
Haiku 4.5 $0.00001 $0.00233

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

Security

Grade A, and why

playwright-testing 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 17d 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.

.cursor/rules/workflows/playwright-testing.mdc · 271 lines

How it starts

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

Playwright Testing Workflow

Invoke with: "test the UI", "write an e2e test", "test in browser", "upstream test", "downstream test"


1. Upstream vs Downstream

This project has two tiers of E2E tests, both in this repo:

Upstream Downstream
Location testing/playwright/e2e/upstream/ testing/playwright/e2e/downstream/
Tag @upstream @downstream
Providers Mocked via API intercepts Real providers (vSphere, oVirt, OpenStack, OVA)
Credentials Not required Requires testing/.providers.json (not in repo)
Data Static fixtures (fixtures/test-data.ts) Dynamic data from real provider inventory
Purpose UI logic, rendering, form flows Full integration -- closest to production
Run npm run test:upstream (in testing/) npm run test:downstream (in testing/)

Downstream tests are the priority -- they exercise real provider connections, actual migrations, and the full UI flow against a real cluster. Upstream tests are useful for fast feedback on UI-only changes.

Upstream is effectively a subset of downstream: upstream covers basic happy paths with mocked data, while downstream covers the same flows plus provider-specific behavior with real infrastructure.


2. Test Directory Structure

For a fuller “how to read this suite” guide (fixtures, intercepts, utils, lint layers), see testing/README.md.

testing/
  playwright/
    e2e/
      upstream/              # Mocked tests (2 files)
      downstream/            # Real provider tests (17+ files)
        providers/
        plans/
        network-maps/
        storage-maps/
    fixtures/                # Test fixtures and helpers
    intercepts/              # API mocking for upstream tests
    page-objects/            # Page Object Model classes
    utils/                   # Utility functions (provider config, helpers)
    types/                   # TypeScript types
    global.setup.ts          # Authentication setup
    global.teardown.ts       # Resource cleanup
  .providers.json.template   # Provider credential template
  e2e.env.template           # Environment variable template
  run-tests.sh               # Containerized test runner (CI/Jenkins)

Read the full file on GitHub · 271 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. 17d ago Changed · +2 lines fc14fc58053e
  2. 1mo ago First seen · 269 lines · 10 tokens per session scan A db9b18edd857

Subscribe to this mod's changes

playwright-testing is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 2,333 once invoked, about $0.0000 per session on Opus 5.5. 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-08-30.