junit-pioneer VS turbine

Schedule (all times UTC): // hosts: 🦁 Ana, 🤖 Nicolai, 🧑🏾‍🏫 Shar // topics: 💻 live code/exploration, 📣 talk, 💬 conversation, 🎮 game: 🤖💻 04:00 working on JUnit Pioneer - https://junit-pioneer.org/ 🤖📣 07:00 "Data-Oriented Programming in Java (21)" 🤖💬 08:00 Gavin Bierman: pattern matching 🤖💻 09:00 exploring JEPs on disallowing dynamic agents (451) and platform integrity (draft 8305968) 🤖💬 10:00 Ron Pressler: platform integrity and the on-ramp 🤖💻 11:00 exploring structured concurrency 🦁📣 12:00 "Growing up with Java" 🦁🎮 13:30 Byte Legend - https://bytelegend.com/ 🧑🏾‍🏫📣 16:00 "Java State of the Union" & "Why Community Matters" 🧑🏾‍🏫💬 17:00 Pratik Patel, Mohammed Aboullaite, Venkat Subramaniam, Andres Almiray, Ixchel Ruiz, Vincent Mayers 🤖💬 19:00 Brian Goetz 🤖💬 20:00 Gunnar Morling 🤖📣 21:00 "Java Next" 🤖💻 22:00 investigating the state of Valhalla 🤖💻 23:00 experimenting with string templates 🤖📣 00:00 talk: "Why don't they just... ?!" 🤖🎮 01:00 Slay the Spire (written in Java!) 🤖💻 02:00 modding Slay the Spire 🤖📣 05:00 "The SolutionFactory To Java's Problems" 🤖📣 06:00 "From Idea to IDE" 🤖💬 07:00 just chatting / AMA 🤖🛏️ 08:00 end

There is a cool library called JUnit Pioneer. It's an extension pack that includes some features that vanilla JUnit lacks. These are cartesian product tests, JSON argument parameterized source, retrying tests and many others. But I'm particularly interested in Issue annotation. Look at the code example below:

junit-pioneer

Much of this is now available in Mockito. Even more - naturally Kotlin doesn’t have static methods, and it’s a good practice not to create them. Ideal code is code that follows the SOLID and Clean Architecture principles, which means it can be easily mocked and tested. Therefore, we, Android developers, don’t need PowerMock’s special features but it’s important to remember that such frameworks exist. Another Mockito’s limitation concerns work with coroutines and flows. In such cases, once again, mockito-kotlin as well as third-party libraries like turbine will help you out. This being said, I’d like to tell you about another alternative to Mockito, which is Mockk.

All you need: https://github.com/cashapp/turbine

You've essentially converged on what Turbine does.

Turbine is an excellent library for testing flows and is pretty much required imo. But overall Rx is much easier to test; debugging works much more consistently and the built in testing functions are great.

turbine release 0.6.0

This issue on how StateFlows should be tested is probably also worth reading: https://github.com/cashapp/turbine/issues/19

Use https://github.com/cashapp/turbine