testing-patterns

testing-patterns is a cursor rule for Cursor from madebyaris/poinf-of-sales. It costs 0 tokens per session (6,526 once invoked), scanned A, original, MIT.

A set of testing rules for a point-of-sale system, covering React components and Go code. It describes unit tests, integration tests, and end-to-end tests, which check individual parts, connected parts, and complete user workflows.

In plain words
What is it for?
Use it when writing or reviewing tests for features such as login, ordering, payment, and kitchen workflows. It includes React Testing Library patterns and Go testing guidance.
Why use it?
It gives developers consistent ways to test business logic, interfaces, APIs, and database interactions. It also helps decide which kind of test belongs at each level.

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 { renderWithProviders } from '../test-utils'.

Good fit Use it when writing or reviewing tests for features such as login, ordering, payment, and kitchen workflows. It includes React Testing Library patterns and Go testing guidance.

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/madebyaris/poinf-of-sales
agentmods
npx agentmods add rules/madebyaris/poinf-of-sales/testing-patterns

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

README.md
[![agentmods](https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/testing-patterns/github.svg)](https://agentmods.dev/rules/madebyaris/poinf-of-sales/testing-patterns)
Your own site
<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/testing-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/testing-patterns/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 testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/testing-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/testing-patterns.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 6,526 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.00000 $0.06526
Opus 5 $0.00000 $0.03263
Sonnet 5 $0.00000 $0.01305
Haiku 4.5 $0.00000 $0.00653

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

Security

Grade A, and why

testing-patterns 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 10d 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-patterns.mdc · 977 lines

How it starts

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

🧪 Testing Patterns & Best Practices

🎯 Testing Philosophy

Testing Pyramid for POS System

    E2E Tests (Few)
    ↑ Full user workflows
    ↑ Critical business flows
    
  Integration Tests (Some)
  ↑ API + Database interactions
  ↑ Component + API integration
  
    Unit Tests (Many)
    ↑ Individual functions
    ↑ Component behavior
    ↑ Business logic validation

Test Coverage Targets

  • Unit Tests: 80%+ coverage for business logic
  • Integration Tests: All API endpoints with database
  • E2E Tests: Core user journeys (login → order → payment → kitchen)

⚛️ Frontend Testing Patterns (React Testing Library)

Component Testing Setup

// test-utils.tsx - Custom testing utilities
import { render, RenderOptions } from '@testing-library/react'
import { QueryClient, QueryClientProvider } from '@tanstack/react-query'
import { ReactElement } from 'react'
import { BrowserRouter } from '@tanstack/react-router'

// Create a test query client with no retries
const createTestQueryClient = () => new QueryClient({
  defaultOptions: {
    queries: {
      retry: false,      // Don't retry on test failures
      gcTime: Infinity,  // Keep data in cache
    },
    mutations: {
      retry: false,
    },
  },
})

interface CustomRenderOptions extends Omit<RenderOptions, 'wrapper'> {
  queryClient?: QueryClient
  initialEntries?: string[]
}

// Custom render with providers
export const renderWithProviders = (
  ui: ReactElement,
  {
    queryClient = createTestQueryClient(),
    initialEntries = ['/'],
    ...renderOptions
  }: CustomRenderOptions = {}
) => {
  const Wrapper = ({ children }: { children: React.ReactNode }) => (
    <QueryClientProvider client={queryClient}>
      <BrowserRouter initialEntries={initialEntries}>
        {children}
      </BrowserRouter>
    </QueryClientProvider>
  )

  return { ...render(ui, { wrapper: Wrapper, ...renderOptions }), queryClient }
}

// Re-export everything
export * from '@testing-library/react'

Read the full file on GitHub · 977 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. 10d ago First seen · 977 lines · 6,526 tokens per session scan A b557e4710417

Subscribe to this mod's changes

testing-patterns is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (140 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,526 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.