Thank you for that. I’m still using Mockito in my projects, but very close to switching to Mockk. This gets rid of one reason not to 😉
For assertions, you should check out Atrium. Very fluent assertions with excellent reporting and features.
👍 1
Mike
10/05/2018, 10:29 AM
and no, I’m not affiliated with it, just very impressed with it as I am with Mockk.
d
darych
10/05/2018, 10:39 AM
Thank you @Mike will check the Atrium. Do you use it in production code?
m
Mike
10/05/2018, 11:44 AM
Not yet. I’m in a large corporation, and starting a spearhead of Kotlin development so I’m only slowly introducing fully Kotlin libraries.
Migrating to Microservices from mega monolith, and bringing new teams up to speed on ‘everything’ service.
Currently, sticking more to Java libraries just in case they get forced back to Java. At least they’ll be familiar with some helpful libraries. So I’m still using Mockito and AssertJ rather than Mockk and Atrium.
I’m up to 2 teams, and they’re helping to spread the word, so hopefully soon I’ll introduce Mockk and Atrium to the projects.
d
darych
10/05/2018, 11:46 AM
I'm working in large company too. I discussed with my management and they gave an approve to use Kotlin in new product with microservices 🙂
Hope you'll be successful and move teams to Kotlin! 🙂
m
Mike
10/05/2018, 12:29 PM
You too! I definitely prefer coding in Kotlin over Java. Java’s not terrible (or at least I’m used to it), but I much prefer to read Kotlin code…