<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i" -->

---
title: Testing Spring Boot Applications Demystified by Philip...
description: A conference talk frames Spring Boot testing as a labyrinth with three bosses: unit testing, slice testing, and integration testing, plus three optimization...
canonical: https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026 | daily.dev
og:description: A conference talk frames Spring Boot testing as a labyrinth with three bosses: unit testing, slice testing, and integration testing, plus three optimization...
og:url: https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i
og:image: https://api.daily.dev/og/posts/pco0UEH3i.png
og:image:alt: Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026

**[Spring I/O](https://daily.dev/sources/springio)** · 52 min read · 0 upvotes · 0 comments

## Summary

A conference talk frames Spring Boot testing as a labyrinth with three bosses: unit testing, slice testing, and integration testing, plus three optimization techniques (context caching, test parallelization, mutation testing). It covers the Spring Boot Starter Test toolbox (JUnit, Mockito, AssertJ, Awaitility, JSON Path), demonstrates MockMvc-based slice testing for controllers, explains Testcontainers for integration tests, and shows how Spring's context cache can cut build times dramatically (one client went from 26 to 12 minutes). It closes with mentions of Spring Boot 4/JUnit 6/Testcontainers 2.0 testing improvements and the speaker's book, workshops, and open-source Spring Test Profiler tool.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.youtube.com/watch?v=DPi2Borv96I>

## Questions this post answers

### What testing improvements does Spring Boot 4 bring compared to previous versions?

Spring Boot 4 upgrades to JUnit 6 and Testcontainers 2.0, adds a new REST test client, and introduces context pausing so cached application contexts no longer keep running message queues or scheduled tasks in the background, preventing them from interfering with other tests' data. Prior to this change, all cached contexts stayed active and could steal each other's messages or corrupt shared test data.

_Teams planning a Spring Boot 4 upgrade can track testing-related changes like these on daily.dev._

### How does Spring's test context caching work and how much can it speed up a test suite?

Spring caches an already-started application context keyed by a merged context configuration object built from things like active profiles, overridden properties, and mocked beans; if a later test needs an identical configuration, Spring hands back the cached context instead of rebuilding it, turning a multi-second startup into a few hundred milliseconds. One real project cut its build time from 26 minutes to 12 minutes by optimizing cache reuse alone, without adding parallelization.

_Developers chasing faster CI pipelines can follow test-suite optimization techniques like this via daily.dev._

### Why doesn't a unit test on a Spring Boot REST controller catch bugs in path mapping, bean validation, serialization, or security?

A unit test invokes the controller's public method directly in plain Java, bypassing HTTP routing, Spring's dispatcher servlet, bean validation, JSON serialization, and Spring Security checks entirely, so bugs in URL mapping, invalid payload rejection, field naming changes (e.g. after a Jackson version bump), or missing authentication checks go undetected. Slice testing with tools like MockMvc is needed to cover these concerns.

_Anyone deciding between unit and slice testing strategies for Spring Boot can dig into comparisons like this on daily.dev._

## Similar posts on daily.dev

- [Crafting Spring Boot Starters](https://daily.dev/posts/crafting-spring-boot-starters-fxxg2w0lt) · Wim Deblauwe · 1 upvotes · 0 comments
- [Conferences](https://daily.dev/posts/conferences-9o3krpinf) · SivaLabs · 0 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#java](https://daily.dev/tags/java), [#spring-boot](https://daily.dev/tags/spring-boot)

[View this post on daily.dev](https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026","url":"https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i"},"datePublished":"2026-09-27T07:26:32.994Z","dateModified":"2026-09-27T07:53:07.119Z","description":"A conference talk frames Spring Boot testing as a labyrinth with three bosses: unit testing, slice testing, and integration testing, plus three optimization...","image":"https://i.ytimg.com/vi/DPi2Borv96I/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/DPi2Borv96I/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Spring I/O","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Spring I/O","logo":"https://media.daily.dev/image/upload/s--e-TcwM9B--/f_auto,q_auto/v1790493985/logos/springio?_a=BAMAMicg0","url":"https://daily.dev/sources/springio"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,java,spring-boot","timeRequired":"PT52M","video":{"@type":"VideoObject","name":"Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026","description":"A conference talk frames Spring Boot testing as a labyrinth with three bosses: unit testing, slice testing, and integration testing, plus three optimization...","thumbnailUrl":"https://i.ytimg.com/vi/DPi2Borv96I/sddefault.jpg","uploadDate":"2026-09-27T07:26:32.994Z","duration":"PT52M","url":"https://api.daily.dev/r/pco0UEH3i","embedUrl":"https://www.youtube.com/embed/DPi2Borv96I"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Spring I/O","item":"https://daily.dev/sources/springio"},{"@type":"ListItem","position":3,"name":"Testing Spring Boot Applications Demystified by Philip Riecks @ Spring I/O 2026"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/testing-spring-boot-applications-demystified-by-philip-riecks-spring-i-o-2026-pco0ueh3i#faq","mainEntity":[{"@type":"Question","name":"What testing improvements does Spring Boot 4 bring compared to previous versions?","acceptedAnswer":{"@type":"Answer","text":"Spring Boot 4 upgrades to JUnit 6 and Testcontainers 2.0, adds a new REST test client, and introduces context pausing so cached application contexts no longer keep running message queues or scheduled tasks in the background, preventing them from interfering with other tests' data. Prior to this change, all cached contexts stayed active and could steal each other's messages or corrupt shared test data. Teams planning a Spring Boot 4 upgrade can track testing-related changes like these on daily.dev."}},{"@type":"Question","name":"How does Spring's test context caching work and how much can it speed up a test suite?","acceptedAnswer":{"@type":"Answer","text":"Spring caches an already-started application context keyed by a merged context configuration object built from things like active profiles, overridden properties, and mocked beans; if a later test needs an identical configuration, Spring hands back the cached context instead of rebuilding it, turning a multi-second startup into a few hundred milliseconds. One real project cut its build time from 26 minutes to 12 minutes by optimizing cache reuse alone, without adding parallelization. Developers chasing faster CI pipelines can follow test-suite optimization techniques like this via daily.dev."}},{"@type":"Question","name":"Why doesn't a unit test on a Spring Boot REST controller catch bugs in path mapping, bean validation, serialization, or security?","acceptedAnswer":{"@type":"Answer","text":"A unit test invokes the controller's public method directly in plain Java, bypassing HTTP routing, Spring's dispatcher servlet, bean validation, JSON serialization, and Spring Security checks entirely, so bugs in URL mapping, invalid payload rejection, field naming changes (e.g. after a Jackson version bump), or missing authentication checks go undetected. Slice testing with tools like MockMvc is needed to cover these concerns. Anyone deciding between unit and slice testing strategies for Spring Boot can dig into comparisons like this on daily.dev."}}]}
```

