<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Testing on 1Stop</title><link>https://blogs.rameskum.com/tags/testing/</link><description>Recent content in Testing on 1Stop</description><image><title>1Stop</title><url>https://blogs.rameskum.com/images/og-default.png</url><link>https://blogs.rameskum.com/images/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 08:50:00 -0400</lastBuildDate><atom:link href="https://blogs.rameskum.com/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>JUnit 6 Just Landed in Your Spring Boot 4.1 BOM: What Actually Changed</title><link>https://blogs.rameskum.com/posts/junit-6-spring-boot-4/</link><pubDate>Mon, 21 Sep 2026 08:50:00 -0400</pubDate><guid>https://blogs.rameskum.com/posts/junit-6-spring-boot-4/</guid><description>Spring Boot 4.1 manages JUnit 6 (6.0.3 on 4.1.0, 6.1.3 on 4.1.1) — and for most apps the upgrade is deleting version pins. What&amp;#39;s new, what was removed, the three things that actually break (Alphanumeric ordering, Store.getOrComputeIfAbsent, CsvFileSource lineSeparator), plus the Surefire and JaCoCo bumps your build needs.</description></item></channel></rss>