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.
git clone --depth 1 https://github.com/madebyaris/poinf-of-salesnpx agentmods add rules/madebyaris/poinf-of-sales/testing-patternsWrote 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.
[](https://agentmods.dev/rules/madebyaris/poinf-of-sales/testing-patterns)<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.
<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>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.06526 |
| Opus 5 | $0.00000 | $0.03263 |
| Sonnet 5 | $0.00000 | $0.01305 |
| Haiku 4.5 | $0.00000 | $0.00653 |
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.
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'
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.
- 10d ago First seen · 977 lines · 6,526 tokens per session scan A b557e4710417
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.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
tester
Tester role - Unit, E2E, and visual regression testing.