testing

Optional testing rules for Spring Boot projects, a Java framework commonly used to build web services. They define test types and the annotations and test settings used for each one.

In plain words
What is it for?
Use them when editing a project that has adopted this Spring Boot profile. They cover tests with Mockito, Spring MVC, MyBatis, and the full Spring application context.
Why use it?
They provide consistent guidance for unit, controller, database-mapper, and full-application tests. They also help keep integration-test settings shared and prevent unexplained local overrides.

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/kyungseo/ai-workflow-harness/testing
Clone the repo
git clone --depth 1 https://github.com/kyungseo/ai-workflow-harness

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 565 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.00565
Opus 5 $0.00000 $0.00282
Sonnet 5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 3d ago against content hash 1221f1bf2f46, 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 3d 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 · 62 lines

How it starts

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

Optional Spring Boot Testing Rules

These rules are not part of the generic AI Workflow Harness core. They are kept as an optional example/profile surface for projects that adopt the harness with Spring Boot backend tests.

Test Layer Annotations

Layer Annotation Context
Unit @ExtendWith(MockitoExtension.class) + @MockitoSettings(strictness = Strictness.LENIENT) No Spring context
Controller slice @WebMvcTest + @ActiveProfiles("test") Spring MVC only
MyBatis slice @MybatisTest + @ActiveProfiles("test") MyBatis mapper only
Integration @SpringBootTest + @AutoConfigureMockMvc + @ActiveProfiles("test") Full Spring context

Integration Test Infrastructure

Prefer the adopted project's established integration-test infrastructure.

MUST:

  • Keep integration-test environment settings in shared test configuration, not per-test ad hoc system properties.
  • Reuse the established integration-test infrastructure pattern in existing service tests.
  • Record infrastructure changes through the adopted project's decision process.

NEVER:

  • Reintroduce local-only test overrides without an explicit decision.
  • Depend on separately running local services for integration tests unless the adopted project documents that requirement.

Assertion and Mocking Style

MUST:

  • Use AssertJ: assertThat(...), assertThatThrownBy(...)
  • Prefer BDD style: given(mock).willReturn(value) over Mockito when/thenReturn
  • Keep @MockitoSettings(strictness = Strictness.LENIENT) — project standard; do not remove without reason.

NEVER:

  • Use JUnit 5 raw assertions (assertEquals, assertTrue) — replace with AssertJ
  • Use @Data on mock objects
  • Use @Autowired field injection in test classes — use constructor injection if needed

Naming Conventions

  • Method name: methodName_scenario_expectedBehavior (English)
  • @DisplayName: Korean display names are intentional. Do not translate existing display names to English.
  • Test class name: {TargetClass}Test

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

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository kyungseo/ai-workflow-harness (13 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 565 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.

Related

Other cursor rules, from other repositories

language-agnostic-patterns

Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.

madebyaris/advance-minimax-m3-cursor-rules · 37 tokens

cursor-tools-mastery

Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.

madebyaris/advance-minimax-m3-cursor-rules · 36 tokens

fable5-coding-craft

Fable 5 coding craft: locate-before-write, root-cause method, simplicity taste, error-handling philosophy, test integrity, refactoring discipline, and counters to common LLM coding failure modes. Load when writing, refactoring, debugging, or reviewing non-trivial code in any language.

madebyaris/advance-minimax-m3-cursor-rules · 60 tokens

cursor-agent-orchestration

Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.

madebyaris/advance-minimax-m3-cursor-rules · 39 tokens

fable5-reasoning

Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.

madebyaris/advance-minimax-m3-cursor-rules · 60 tokens

cursor-mcp-optimization

Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.

madebyaris/advance-minimax-m3-cursor-rules · 32 tokens