testing

A set of project rules for automated tests, including Jest tests for individual pieces of code and Playwright tests for browser-based end-to-end behaviour.

In plain words
What is it for?
Use it when adding or reviewing tests for web components and utilities, especially tests that simulate user interaction in a browser.
Why use it?
It gives tests a consistent location, naming style and structure, including checks for rendering, user actions, loading and error states.

Cursor rule for Cursor

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.

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

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,128 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01128
Opus 5 $0.00000 $0.00564
Sonnet 5 $0.00000 $0.00226
Haiku 4.5 $0.00000 $0.00113

Measured 2d ago against content hash fa5c4664a3dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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/testing.mdc · 164 lines

How it starts

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

Testing Guidelines (Supplement)

For basic testing approach (Jest for unit, Playwright for E2E), see AGENTS.md. This rule adds detailed patterns.


1. Unit Tests (Jest)

File Location

  • Place test files in __tests__ folder adjacent to the module being tested
  • Naming: ComponentName.test.tsx or utilName.test.ts

Structure

import { render, screen } from '@testing-library/react';
import { userEvent } from '@testing-library/user-event';

describe('ComponentName', () => {
  it('renders correctly with valid props', () => {
    render(<Component {...defaultProps} />);
    expect(screen.getByText('Expected text')).toBeInTheDocument();
  });

  it('handles user interactions', async () => {
    const user = userEvent.setup();
    render(<Component {...defaultProps} />);
    await user.click(screen.getByRole('button'));
    await user.type(screen.getByLabelText('Name'), 'test-value');
    expect(screen.getByDisplayValue('test-value')).toBeInTheDocument();
  });

  it('handles loading state', () => {
    render(<Component loaded={false} />);
    expect(screen.getByRole('progressbar')).toBeInTheDocument();
  });

  it('handles error state', () => {
    render(<Component loadError={new Error('Failed')} />);
    expect(screen.getByText(/failed/i)).toBeInTheDocument();
  });

  it('handles empty state', () => {
    render(<Component data={[]} />);
    expect(screen.getByText(/no items/i)).toBeInTheDocument();
  });
});

Mocking

// Mock i18n
jest.mock('src/utils/i18n', () => ({
  useForkliftTranslation: () => ({ t: (key: string) => key }),
}));

// Mock Console SDK
jest.mock('@openshift-console/dynamic-plugin-sdk', () => ({
  useK8sWatchResource: jest.fn(),
}));

What to Test

  • Renders without error
  • Displays correct data
  • Handles loading, error, empty states
  • User interactions trigger correct callbacks
  • Edge cases (null data, empty arrays, boundary values)

Run Commands

npm test                         # Run all unit tests
npm run test:coverage            # With coverage report
npm test path/to/file.test.ts    # Run specific test file

Read the full file on GitHub · 164 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. 2d ago First seen · 164 lines · 0 tokens per session scan A fa5c4664a3dc

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,128 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-08-30.