<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kotlin on Neat Guy Coding</title><link>https://neatguycoding.com/tags/kotlin/</link><description>Recent content in Kotlin on Neat Guy Coding</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 NeatGuyCoding</copyright><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://neatguycoding.com/tags/kotlin/index.xml" rel="self" type="application/rss+xml"/><item><title>Supercharging Spring Boot Tests with Kotlin Expressiveness: Assertions, Fixtures, and Reactive Boundaries</title><link>https://neatguycoding.com/posts/supercharge-spring-boot-tests-with-kotlin-dsl-power-by-urs-peter-spring-io-202/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://neatguycoding.com/posts/supercharge-spring-boot-tests-with-kotlin-dsl-power-by-urs-peter-spring-io-202/</guid><description>Spring Boot and Kotlin interoperate maturely on the JVM; teams often introduce Kotlin first in &lt;code>src/test&lt;/code>, applying extension functions, default parameters, type-safe DSLs, and assertion styles such as Kotest in integration tests and &lt;code>MockMvc&lt;/code> scenarios to cut boilerplate and tighten failure messages. Meanwhile, Java builders, overloaded static helpers, and Project Reactor’s &lt;code>StepVerifier&lt;/code> each carry their own cognitive cost; the article organizes common motivations by dependency layer, alignable public APIs, and semantic boundaries to watch (e.g. JVM type erasure, whether reactive verification truly completes subscription).</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://neatguycoding.com/posts/supercharge-spring-boot-tests-with-kotlin-dsl-power-by-urs-peter-spring-io-202/cover.png"/></item></channel></rss>