<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/integration/</link><description>Recent content in Integration on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 17 Dec 2025 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimizing Spring Integration Tests at Scale</title><link>https://javapro-en.svenruppert.com/optimizing-spring-integration-tests-at-scale/</link><pubDate>Wed, 17 Dec 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/optimizing-spring-integration-tests-at-scale/</guid><description>&lt;h2 id="1-introduction"&gt;1. Introduction&lt;/h2&gt;
&lt;p&gt;Sprint Boot is a popular Java framework that provides a rich platform for integration testing. It&amp;rsquo;s pretty convenient and flexible; however, at a large scale, when the project has hundreds or even thousands of integration tests using lots of heavy components (like TestContainers-managed beans), there can be performance and other issues. &lt;strong&gt;There are many hidden details that make much sense when the codebase becomes bigger and the configuration becomes more complicated.&lt;/strong&gt; In this article, we&amp;rsquo;ll look at how the framework works under the hood, why it can be slow and inefficient, and how to boost the performance.&lt;/p&gt;</description></item></channel></rss>