Instancio 6.0.0-RC2 is out! This release includes improved Kotlin support through the new instancio-kotlin dependency. Any feedback would be appreciated! github.com/instancio/inst…
We're looking to improve Instancio's API for Kotlin users and would love your input! If you use Kotlin, please share your feedback: github.com/instancio/inst…
Claude just made the test suite pass by rewriting the failing test to test only part of the functionality --while retaining the original name, which implied the more stringent test
🤔 Who said that AssertJ 3 is in maintenance mode?
📢 We're planning an exceptional 3.28 release – let us know what you'd like to see in there! 👇
github.com/orgs/assertj/d…
Slash your @springframework integration test times! ⚡
Waiting forever for builds? Spring Test Profiler reveals why your Spring TestContext Caching is missing its mark.
✅ Identify cache misses
✅ Optimize test context reuse
✅ Get faster feedback
Free & open-source!
github.com/PragmaTech-Gmb…
Instancio 5.5.0 is out! This release includes minor enhancements/fixes and housekeeping items.
Next major release of Instancio, v6, will be based on Java 17 as the baseline.
github.com/instancio/inst…
Testing Spring Boot controllers is a balancing act!
Skip flaky unit tests & slow full-blown tests - learn how AtWebMvcTest enables fast, HTTP-aware testing and boosts your confidence ⚡️.
rieckpil.de/how-to-test-sp…#SpringBoot#Testing
It’s Here: the Java Testing Toolbox eBook v1.0 is Now Available! 🧪
The wait is over! 🎉
My new eBook "30 Testing Tools and Libraries Every Java Developer Must Know" (aka. Java Testing Toolbox) has officially launched 🚀
This final release of the Java Testing Toolbox covers 30 essential testing tools, including 9 brand-new chapters on:
✅ Pact – Contract testing for microservices
✅ Awaitility – Fluent async testing
✅ @diffbluehq - AI-powered test generation
✅ @SeleniumHQ – UI testing automation
✅ @archtests – Enforcing architecture rules
✅ @instancio_java – Smart test data generation
✅ JMH – Benchmarking Java code
✅ JfrUnit – Testing with Java Flight Recorder
✅ PIT – Mutation testing for better coverage
The other 21 testing tools include: TestNG, Mockito, WireMock, REST Assured, @localstack, @testcontainers, @wiremockorg, @selenide, @junitteam, @GatlingTool, @MockitoJava, JGiven, Spock, Microshed Testing, ApacheBench, GreenMail, MockWebServer, Spock, Hamcrest, AssertJ, JSONAssert, JsonPath, XMLUnit 🧰
Why This eBook is a Must-Have:
- Covers both popular and niche Java testing tools
- Practical setup guides for Maven & Gradle
- Focuses on the 20% of features you’ll use 80% of the time
- Beginner-friendly with hands-on examples
- Lifetime updates to keep your testing skills sharp
📢 Already got the eBook on Leanpub? You can download the new version for free!
Didn’t get notified? DM me
If you haven’t grabbed your copy yet, now’s the best time to level up your Java testing skills!
rieckpil.de/testing-tools-…
WORKSHOP @ Digit 2025 ✍️
“Smarter testing with Snapshot Testing, Instancio and “Millibenchmarking”” by Kristo Koert, the Technical Lead @ @twilio
More about this workshop 👉 digit.dev/workshops/#digitconf
@stefanocodes The biggest reason for AssertJ would be codebase improvements. However, if you continue supporting Java 8 after upgrading, then you will need to backport bug fixes, which adds extra maintenance effort.
@stefanocodes Tough question to answer given how popular AssertJ is. According to new relic's statistics Java 8 is at 28.8% (vs 35.4% for Java 17) in 2024, still a significant number.
For AssertJ 4, we wanted to upgrade to Java 17, but we are discussing whether to stay on 8 or go to 11.
The main reason is to keep our effort reasonable and continue supporting users who cannot upgrade (e.g., RHEL 7 users under ELS).
Any strong reason to keep upgrading to 17?