<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JUnit on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/junit/</link><description>Recent content in JUnit on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 14 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/junit/index.xml" rel="self" type="application/rss+xml"/><item><title>8. Test Lifecycle Management and Hooks</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/08-test-lifecycle-management/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/08-test-lifecycle-management/</guid><description>&lt;h2 id="introduction-to-test-lifecycle-management"&gt;Introduction to Test Lifecycle Management&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow explorers of robust testing! In previous chapters, we learned the magic of spinning up disposable containers to test our applications with real dependencies. We&amp;rsquo;ve seen how Testcontainers simplifies setting up databases like PostgreSQL and message brokers like Kafka, freeing us from the shackles of mocks and in-memory fakes.&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s a thought: What happens to these containers after our tests run? And what if starting a new container for &lt;em&gt;every single test method&lt;/em&gt; slows down our test suite to a crawl? This is where Testcontainers&amp;rsquo; lifecycle management truly shines.&lt;/p&gt;</description></item><item><title>4. Core API: Generic Containers and Specific Modules</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/04-core-api-generic-specific-modules/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/04-core-api-generic-specific-modules/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our previous chapters, we learned &lt;em&gt;why&lt;/em&gt; Testcontainers is a game-changer for robust, reliable integration and end-to-end testing. We understood how it leverages Docker to provide disposable, real-world dependencies without the headaches of managing complex test environments or falling into the trap of unreliable mocks.&lt;/p&gt;
&lt;p&gt;Now, it&amp;rsquo;s time to roll up our sleeves and explore the &lt;em&gt;how&lt;/em&gt;. This chapter dives deep into the heart of Testcontainers: its Core API. We&amp;rsquo;ll uncover two powerful ways to interact with Docker containers for your tests: using &lt;code&gt;GenericContainer&lt;/code&gt; for ultimate flexibility with any Docker image, and leveraging specialized &amp;ldquo;Modules&amp;rdquo; that offer convenient, idiomatic APIs for common services like databases and message brokers. By the end, you&amp;rsquo;ll be confidently spinning up and managing containerized services across Java, JavaScript, and Python.&lt;/p&gt;</description></item></channel></rss>