What is testing-strategy?

A testing plan for the Rakit UI AI design-selection tool. It covers small function tests, tests of connected components, and full browser tests using Playwright.

Use it to organize tests for server behavior, HTML generation, design selection, error handling, timeouts, and browser interactions. It also covers testing multiple users at the same time.

It separates different kinds of failures and checks both individual code and complete user flows. This helps catch errors in validation, servers, templates, recovery, and simultaneous sessions.

testing-strategy — Cursor rule for Cursor by madebyaris/rakitui-ai

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/madebyaris/rakitui-ai

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/madebyaris/rakitui-ai/testing-strategy/github.svg)](https://agentmods.dev/rules/madebyaris/rakitui-ai/testing-strategy)

Your own site

<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/testing-strategy"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/testing-strategy/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/madebyaris/rakitui-ai/testing-strategy"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/testing-strategy.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 384 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.00384
Opus 5.5	$0.00000	$0.00154
Sonnet 5.5	$0.00000	$0.00077
Haiku 4.5	$0.00000	$0.00038

Measured 1mo ago against content hash 728ca4ffbbdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-strategy 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 1mo 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-strategy.mdc · 81 lines

What it actually says

Testing Strategy

Comprehensive testing approach for the Rakit UI AI design selection tool.

Test Structure

tests/
├── unit/
│   ├── DesignselectionTool.test.ts
│   ├── serverUtils.test.ts
│   └── designSelection.test.ts
├── integration/
│   └── selection-flow.test.ts
└── e2e/
    └── browser-selection.test.ts

Unit Testing

Test individual functions in isolation:

DesignselectionTool Tests

Test schema validation
Test execute method with various inputs
Test error handling
Mock dependencies (serverUtils)

ServerUtils Tests

Test server creation and port handling
Test state management functions
Test cleanup mechanisms
Mock HTTP server and file system

Template Tests

Test HTML generation with different inputs
Test XSS prevention
Test template escaping

Integration Testing

Test component interactions:

Server startup and shutdown flow
Selection process end-to-end
Error recovery mechanisms
Timeout handling

E2E Testing

Test full user flows using Playwright:

Browser opens correctly
Design options display properly
Selection process works
Browser closes after selection
Multiple simultaneous sessions

Testing Tools

Jest: Unit and integration tests
Playwright: E2E browser tests
Supertest: HTTP endpoint testing
Mock Service Worker: API mocking

Coverage Goals

Unit tests: 80% coverage minimum
Integration tests: Critical paths covered
E2E tests: Happy path + key error scenarios

CI/CD Integration

Run tests on every pull request
Block merging if tests fail
Generate coverage reports
Performance benchmarking

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.

1mo ago First seen · 81 lines · 0 tokens per session scan A 728ca4ffbbdb

Subscribe to this mod's changes

testing-strategy is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 384 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-31.

E2E testing Testing Unit testing ai-tools component-library design-tools frontend-tools mcp model-context-protocol

testing-strategy