<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testcontainers on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/testcontainers/</link><description>Recent content in Testcontainers 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/testcontainers/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><item><title>MockServer NeoLight: A Lightweight Alternative for API Testing with Testcontainers</title><link>https://javapro-en.svenruppert.com/mockserver-neolight-a-lightweight-alternative-for-api-testing-with-testcontainers/</link><pubDate>Fri, 17 Oct 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/mockserver-neolight-a-lightweight-alternative-for-api-testing-with-testcontainers/</guid><description>&lt;p&gt;The open-source project &lt;a href="https://github.com/xdev-software/mockserver-neolight"&gt;MockServer NeoLight&lt;/a&gt; has been released as a lightweight rewrite of the original &lt;a href="https://github.com/mock-server/mockserver"&gt;MockServer&lt;/a&gt;. Its primary focus lies on &lt;strong&gt;simplicity&lt;/strong&gt;, &lt;strong&gt;maintainability&lt;/strong&gt;, and seamless integration with &lt;a href="https://java.testcontainers.org/"&gt;&lt;strong&gt;Testcontainers&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The MockServer concept allows developers to mock HTTP and HTTPS requests in order to &lt;strong&gt;simulate APIs for testing purposes&lt;/strong&gt;. By setting expectations for incoming requests and defining responses, it creates controlled environments for integration testing. This isolates the system under test from real external dependencies, leading to predictable and repeatable results.&lt;/p&gt;</description></item><item><title>Supercruising with Testcontainers: Making Tests Faster and More Flexible</title><link>https://javapro-en.svenruppert.com/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/</link><pubDate>Fri, 10 Oct 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/</guid><description>&lt;p&gt;&lt;strong&gt;Testcontainers&lt;/strong&gt; has become an essential tool in many Java projects to run integration and system tests in realistic environments. However, when test scenarios grow complex, developers often run into limitations—especially around configuration, parallelization, and resource usage. An open-source framework built on top of Testcontainers addresses some of these challenges with powerful extensions.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/xdev-software/tci-base"&gt;&lt;strong&gt;Testcontainers Infrastructure (TCI) Framework&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="1-improve-customizability-and-parallelization"&gt;&lt;strong&gt;1. Improve customizability and parallelization&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;By using the factory pattern when creating containers, the goal is to make it easier for developers to adjust the containers as needed.&lt;/p&gt;</description></item><item><title>Building Local LLM AI-Powered Applications with Quarkus, Ollama, and Testcontainers</title><link>https://javapro-en.svenruppert.com/build-local-llm-ollama-quarkus-testcontainers/</link><pubDate>Tue, 09 Sep 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/build-local-llm-ollama-quarkus-testcontainers/</guid><description>&lt;p&gt;Traditionally, many AI-powered applications rely on cloud-based APIs or centralized services for model hosting and execution. While this approach has its advantages, such as scalability and ease of use, it also introduces challenges around latency, data privacy, and dependency on third-party providers.&lt;/p&gt;
&lt;p&gt;This is where local AI models shine. By running models directly within your application&amp;rsquo;s infrastructure, you gain greater control over performance, data security, and deployment flexibility. However, building such systems requires the right tools and frameworks to bridge the gap between traditional software development and AI model integration.&lt;/p&gt;</description></item></channel></rss>