311-frameworks-spring-boot-slice-testing

A set of guidelines for testing individual parts of a Spring Boot application, such as web endpoints, database access, or JSON handling, without starting the whole application.

In plain words
What is it for?
Use it to structure focused tests with Spring Boot slice annotations, mock dependencies, configure test profiles, and create custom test setups.
Why use it?
It avoids slow, broad tests when you only need to check one layer. This makes failures easier to understand and gives faster feedback.

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/jabrena/cursor-rules-spring-boot/311-frameworks-spring-boot-slice-testing
Clone the repo
git clone --depth 1 https://github.com/jabrena/cursor-rules-spring-boot

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,621 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.02621
Opus 5 $0.00000 $0.01311
Sonnet 5 $0.00000 $0.00524
Haiku 4.5 $0.00000 $0.00262

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

Security

Grade A, and why

311-frameworks-spring-boot-slice-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/311-frameworks-spring-boot-slice-testing.mdc · 415 lines

How it starts

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

Spring Boot Slice Testing

Spring Boot slice testing allows you to test specific layers or "slices" of your application in isolation, providing faster and more focused tests than full integration tests. This approach helps maintain test clarity, reduces test execution time, and improves maintainability.

Implementing These Principles

These guidelines are built upon the following core principles:

  • Layer Isolation: Test each application layer independently without loading the entire Spring context
  • Focused Testing: Use appropriate slice annotations to load only the components needed for specific functionality
  • Mock Dependencies: Mock external dependencies and other layers to achieve true unit testing at the slice level
  • Fast Execution: Minimize Spring context loading to achieve rapid test feedback cycles

Table of contents

  • Rule 1: Use @WebMvcTest for Web Layer Testing
  • Rule 2: Use @JdbcTest for Repository Layer Testing
  • Rule 3: Use @JsonTest for JSON Serialization Testing
  • Rule 4: Use @MockBean for Mocking Dependencies
  • Rule 5: Configure Test Profiles Appropriately
  • Rule 6: Use @TestConfiguration for Custom Test Setup

Rule 1: Use @WebMvcTest for Web Layer Testing

Title: Test Controllers in Isolation with @WebMvcTest Description: Use @WebMvcTest to test only the web layer (controllers) without loading the full application context. This annotation configures Spring MVC infrastructure and auto-configures MockMvc for testing HTTP requests and responses.

Good example:

@WebMvcTest(UserController.class)
class UserControllerTest {

    @Autowired
    private MockMvc mockMvc;
    
    @MockBean
    private UserService userService;
    
    @Test
    void shouldReturnUserWhenValidId() throws Exception {
        // Given
        User user = new User(1L, "John Doe", "[email protected]");
        when(userService.findById(1L)).thenReturn(user);
        
        // When & Then
        mockMvc.perform(get("/api/users/1"))
            .andExpect(status().isOk())
            .andExpect(jsonPath("$.name").value("John Doe"))
            .andExpect(jsonPath("$.email").value("[email protected]"));
    }
}

Read the full file on GitHub · 415 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 · 415 lines · 0 tokens per session scan A 406c29192fd0

Subscribe to this mod's changes

311-frameworks-spring-boot-slice-testing is a cursor rule published in the GitHub repository jabrena/cursor-rules-spring-boot (47 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,621 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.