some kotlin stuff made it on the thoughtworks rada...
# feed
d
what is significance of making it to thoughtworks radar list?
m
Many CIO’s (and others) look at the Radar so it can help you in selling the technology to your company. It’s also interesting to read their perspective on it.
p
honestly I think kotlintest is more useful and solid than spek...
m
I use JUnit Jupiter and AssertJ. Spek2 looks promising, but it’s looked that way for quite awhile. Doesn’t seem to be the momentum behind it to get a GA.
t
I still use Spock, nothing else seems to even come close
m
I agree but can't afford to introduce 2 languages at once. Kotlin is enough of a stretch at a mega Corp. Junit Jupiter is very good and we've created some extensions around assertj to make it more fluent, combined with Kotlin niceness, so I don't miss Spock too much.
t
We were already running Java/Spock so Kotlin was the new language. We’ve all but replaced all our Java now though 😄
m
Yep. One language at a time. I’m already pushing things introducing Kotlin, and was worried about any unusual issues w/Groovy and Kotlin so was reluctant to introduce Spock too. Fortunately JUnit Jupiter came out, so it drastically reduced the pain of JUnit, but I’d still love Spock (or Spokk 😉) for testing.
t
If I could get close to Spock in pure Kotlin I’d make the switch. The language interplays can be challenging at times, but so far we’re considering it worth it
👍 1
p
KotlinTest has nothing to envy from Spock
👍🏻 1
w
ive been using junit5 jupiter . I was using kotlin-test for awhile, but lately I have been using assertk
m
Yeah, too many assertion libraries. assertJ, assertK, Atrium, Kluent, hamkrest, Expekt (although may be dormant), I’ve tended to stay with Java libraries as the teams I’m working with may have to work on Java projects, so at least it’s one less thing they need to learn. Already learning Boot, Cloud, Kotlin, Git, CI/CD etc as they only have real experience in the mainframe world.