Repository navigation
v3.0.0 #802
jak78dkt
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🥒 Announcing Tzatziki 3.0.0: Test your Microservices with Ease!
Hi team! We are thrilled to announce that Tzatziki 3.0.0 is officially out! 🎉
This major milestone marks a huge step forward in our mission to provide the best "off-the-shelf" Cucumber steps for modern microservices architectures.
🌟 What's New?
🍃 NEW: Spring Boot 4 Compatibility: Tzatziki 3.0 is now fully compatible with Spring Boot 4, ensuring a smooth testing experience with the latest features of the Spring ecosystem.
✨ NEW: MCP Support (Model Context Protocol)
You can now test your MCP servers and AI-driven tools as easily as your REST APIs! Tzatziki 3.0 introduces dedicated steps to interact with and assert on MCP flows, making it the first library of its kind to bridge the gap between BDD and the Agentic web.
🔧 Other Updates
• JUnit 6 and TestContainers 2 are now supported, bringing more stability and performance to your test suites.
• Kafka Fix: Resolved a NullPointerException when consuming records with null header values (thanks to Antoine Leveugle! 🙌).
As this is a major version, we’ve cleaned up the library to make it more robust and future-proof:
1️⃣ Deprecations: Dropped support for Spring Boot 3.x. We have created a 2.x branch that remains compatible with Spring Boot 3 but will only receive critical fixes.
2️⃣ Spring Boot 4 & Cucumber Init: Upgrading to JUnit 6 requires a change in how Cucumber is launched and initialized. Don't worry: for most projects, this only involves modifying a single class, and everything is detailed in the migration guide.
3️⃣ Module Removal: The deprecated mockfaster and tzatziki-http-legacy modules have been officially removed. As previously announced, they are replaced by a backward compatible version of tzatziki-http based on Wiremock.
4️⃣ MongoDB Step Renaming: MongoDB steps have been renamed to allow them to co-exist seamlessly with JPA steps in the same project without naming conflicts. Please review this diff for necessary adjustments in your project.
🔮 What’s Next?
We’re not stopping here! Our roadmap for the coming months includes:
• 🤖 Tzatziki AI Skill: A dedicated toolset to help AI agents write high-quality Tzatziki tests autonomously.
• 🚀 tzatziki-kafka : A lightweight, Spring-independent alternative to
tzatziki-spring-kafka. This new module will focus on functional testing by connecting directly to existing Kafka brokers (e.g., in pre-production), thus offering maximum flexibility for validating data flows without a Spring Boot dependency.• 🗄️ tzatziki-sql: A new module for relational data insertion and assertion, completely independent of JPA for better flexibility.
Ambitious roadmap ahead! We rely on your contributions to make it happen.
💬 Feedback & Support
We are eager to hear your thoughts on this new version! Your feedback is essential to keep improving Tzatziki. Should you encounter any issues during your migration or daily use, please reach out - we'll make it a priority to fix them as quickly as possible.
📦 Getting Started
❤️ Thank You
A huge thanks to everyone who helped test the MCP beta and the Spring Boot 4 integration. This release belongs to the community!
Full Changelog
v2.3.10...v3.0.0
Documentation
https://github.com/Decathlon/tzatziki/blob/main/README.md
Stay fresh with Tzatziki! 🥒
This discussion was created from the release v3.0.0.
All reactions