<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TDD on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/tdd/</link><description>Recent content in TDD on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 10 Sep 2025 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/tdd/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering JUnit: Navigating between old and new versions for a smarter test strategy</title><link>https://javapro-en.svenruppert.com/mastering-junit-navigating-between-old-and-new-versions-for-a-smarter-test-strategy/</link><pubDate>Wed, 10 Sep 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/mastering-junit-navigating-between-old-and-new-versions-for-a-smarter-test-strategy/</guid><description>&lt;p&gt;After the JUnit 5 was released, a lot of developers just added this awesome new library in their projects, because unlike others versions, this new version, is not necessary migrate from JUnit 4 to 5, you just need include the new library in your project, and with all the engine of JUnit 5 you can do your new tests using JUnit 5, and the older one with JUnit 4 or 3,  will keep running without problem. &lt;/p&gt;</description></item></channel></rss>