test-create-unit

test-create-unit is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (1,167 once invoked), scanned A, original, MIT.

A set of rules for adding unit tests, which check small pieces of software such as functions, components, API routes, and hooks in isolation.

In plain words
What is it for?
Use it when writing Vitest tests with happy-dom, React Testing Library, user-event, and built-in mocking for components and other small code units.
Why use it?
It keeps new tests consistent with the project’s required tools, file locations, naming conventions, and minimal-change approach.

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/oakensoul/nextjs-cursor-prompts/test-create-unit
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

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 test-create-unit

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/test-create-unit.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/test-create-unit)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/test-create-unit"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/test-create-unit.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,167 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.01167
Opus 5 $0.00000 $0.00583
Sonnet 5 $0.00000 $0.00233
Haiku 4.5 $0.00000 $0.00117

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

Security

Grade A, and why

test-create-unit 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 4d 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/prompts/test/test-create-unit.mdc · 153 lines

How it starts

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

Create Unit Tests

FOCUS: Unit tests for components, server actions, API routes, utilities, and hooks

FOLLOW MINIMAL CHANGE PRINCIPLES: When creating tests, preserve existing code patterns and architecture. Do not modify working code - only add tests alongside existing functionality.

Please create comprehensive unit test coverage for the code I'm working on, following our vitest-based testing standards.

🧪 MANDATORY TESTING FRAMEWORK REQUIREMENTS

Testing Stack (NO EXCEPTIONS)

  • Primary Framework: vitest (NEVER Jest)
  • DOM Environment: happy-dom
  • Component Testing: @testing-library/react
  • User Interactions: @testing-library/user-event
  • Mocking: Built-in vitest mocking capabilities

File Structure & Naming (STRICTLY ENFORCED)

  • Location: Co-located in __tests__/ subdirectories next to components
  • Unit Tests: ComponentName.test.tsx or function-name.test.ts

📋 UNIT TEST REQUIREMENTS

Components Must Test:

  • Basic rendering with default props
  • All prop variations and combinations
  • User interactions (clicks, form input, etc.)
  • Error states and error boundaries
  • Loading states (if applicable)
  • Conditional rendering logic
  • Event handlers and callbacks

Server Actions Must Test:

  • Success cases with valid input
  • Error handling and validation
  • Input sanitization and validation
  • Return value structure and types
  • Side effects (database operations, etc.)

API Routes Must Test:

  • All HTTP methods (GET, POST, PUT, DELETE)
  • Request/response handling
  • Authentication and authorization
  • Input validation and sanitization
  • Error responses and status codes

Utilities/Hooks Must Test:

  • Core functionality and behavior
  • Edge cases and boundary conditions
  • Error conditions and handling
  • All function parameters and return types

🔧 IMPLEMENTATION STANDARDS

Unit Test Template

import { render, screen } from '@testing-library/react'
import userEvent from '@testing-library/user-event'
import { describe, it, expect, vi } from 'vitest'
import { ComponentName } from './ComponentName'

describe('ComponentName', () => {
  it('should render correctly', () => {
    render(<ComponentName />)
    expect(screen.getByRole('button')).toBeInTheDocument()
  })
  
  it('should handle user interactions', async () => {
    const user = userEvent.setup()
    const mockHandler = vi.fn()
    render(<ComponentName onClick={mockHandler} />)
    
    await user.click(screen.getByRole('button'))
    expect(mockHandler).toHaveBeenCalledOnce()
  })
  
  it('should handle error states', () => {
    render(<ComponentName error="Something went wrong" />)
    expect(screen.getByText('Something went wrong')).toBeInTheDocument()
  })
})

Read the full file on GitHub · 153 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. 4d ago First seen · 153 lines · 0 tokens per session scan A 3f85fae52492

Subscribe to this mod's changes

test-create-unit is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,167 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.