Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Spring Boot

A Cursor `.mdc` rule can attach only when you touch tests. This variant keeps testing policy out of the always-on project rule so day-to-day edits stay quieter. This copy is written for a Spring Boot project. This repository is a Spring Boot service. Controllers stay thin, transactions sit on the service the project already uses, and configuration comes from the environment.

The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.

The example assumes Spring Boot with Maven or Gradle, whichever wrapper is in the repo. It does not assume WebFlux versus MVC, or a particular database. Follow the stack that is already on the classpath.

Customize in the generatorBrowse the library

Example file

Balanced strictness, readable style, pragmatic tests. Download name: testing.mdc

---
description: "Testing rules for a Spring Boot repository"
globs: "**/*Test.java"
alwaysApply: false
---

# Testing rules

Attach these rules when editing tests in this Spring Boot repository.
The always-on project rule still lives in `.cursor/rules/project.mdc`. This file does not repeat it.

## Stack

This repository is a Spring Boot service. Controllers stay thin, transactions sit on the service the project already uses, and configuration comes from the environment.

## Commands

- Test: `./mvnw test`
- Run: `./mvnw spring-boot:run`
- Package: `./mvnw package`

Use the script the repo already defines when it differs from the command above.

## Testing

Add or update tests when behavior changes.

Add a sliced test for the controller or service. Do not boot the entire context for a validation rule.

## Done when

- The requested behavior works.
- The module's tests pass. Use the Maven wrapper if it is present, otherwise the Gradle wrapper.
- The diff stays inside the task.
- You list anything you could not run.

Add it to the project

  1. 01

    Copy a starting file

    Copy the example Cursor testing rule on this page, or open the generator if you want different testing, strictness, or comment rules.

  2. 02

    Save it at .cursor/rules/testing.mdc

    Save it at `.cursor/rules/testing.mdc` in the Spring Boot repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

  3. 03

    Start a fresh agent session

    Rules files are read when a session starts. A chat that is already open may still be using the old instructions.

  4. 04

    Give it one small task

    Ask for one change a Spring Boot agent often gets wrong, such as a request DTO with Bean Validation that returns 400 on a bad body. If it ignores the file, confirm the path and start a new session.

Questions about this file

Where do I put Cursor testing rule in a Spring Boot repo?

Save it at `.cursor/rules/testing.mdc` in the Spring Boot repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

Which tools read this Cursor testing rule?

Cursor loads `.cursor/rules/testing.mdc` when a file matches its globs. It does not replace `project.mdc`. Keep the always-on rule for stack conventions.

What does the Spring Boot example assume?

The example assumes Spring Boot with Maven or Gradle, whichever wrapper is in the repo. It does not assume WebFlux versus MVC, or a particular database. Follow the stack that is already on the classpath.

Does VibeSpell upload my repository?

No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.

Other files for Spring Boot

Cursor testing rule for other stacks