```'java.lang.Throwable io.kotest.assertions.eq.EqKt.eq$default(java.lang.Object, java.lang.Object, ...

# kotest

[Peter]

'java.lang.Throwable io.kotest.assertions.eq.EqKt.eq$default(java.lang.Object, java.lang.Object, boolean, int, java.lang.Object)'
java.lang.NoSuchMethodError: 'java.lang.Throwable io.kotest.assertions.eq.EqKt.eq$default(java.lang.Object, java.lang.Object, boolean, int, java.lang.Object)'

this happens when i do x().shouldBeSome("y") ❌
kotest 4.6.3
io.kotest.extensionskotest assertions arrow1.1.1

[sam]

What versions of arrow and kotest-arrow extensions ?

[Peter]

arrow: 1.0.1

[Peter]

maybe i’m missing kotest-arrow-extensions 🤔

[sam]

https://github.com/kotest/kotest-extensions-arrow

[sam]

when arrow released 1.0 a bunch of stuff changed

[Peter]

so i need something in addition to io.kotest.extensions:kotest-assertions-arrow:1.1.1 ?

[sam]

hmmm that should be good

[Peter]

[sam]

ok so 1.1.1 is using kotest 5.0.0.M3

[Peter]

ahhh

[Peter]

how about 1.1.0?

[sam]

looks like the same, probably because arrow 1.0 is now MPP

[sam]

and for that we need Kotest 5.0

[Peter]

gotcha

[Peter]

any idea if kotest 5.0 will be out this year?

[sam]

kotest 5 is just waiting on kotlin 1.6 final

[sam]

so maybe this week, depends when JB release 1.6

[Peter]

excellent .. aren’t we all 😄

[sam]

if you're happy with 1.6 rc2

[sam]

then kotest 5.0.0.M4 is stable

[sam]

I don't think anything else will change between M4 and final

[Peter]

that’s good to know, thank you!

[Peter]

random q: do you use Arrow in your day to day? i’m busy building a library i want to open source and using Arrow quite a bit .. wonder how much that will hinder adoption

[sam]

I don't use it personally

[sam]

For Kotest, I don't use it because I view Kotest as a "base level" dependency for projects. It should be dependency free as much as possible since a lot of community projects rely on it.

[Peter]

ah interesting - if i remember correctly you have a scala background too, just learned to live without the options/eithers & cat theory?

[sam]

No I wrote my own

[Peter]

oh right .. i meant in your professional work (not kotest)

[Peter]

ahh

[sam]

ok for professional....

[sam]

I used to use it but then moved away as each release broke things. Now I understand that as a new library that's bound to happen, but when you're trying to encourage FP adoption amongst colleagues who are perhaps more "java enterprise spring" devs, changing things each release isn't helpful.

[sam]

Now that it's gone 1.0 and the API is locked in, would I use it? absolutely,

[Peter]

hahah… also surrounded by java/springboot colleagues … it’s a slow grind to spread the good word 😉

[sam]

It can be frustrating, but I've had very positive feedback around my preferred stack - ktor for http, my own library for basic FP types (tabby), my own configuration library for immutable config (hoplite) and staying away from DI.

[sam]

And obviously Kotest

[sam]

when I can show people a suite of tests that test a real database against test containers, without a single mock, all in kotest, people generally come away convinced

[sam]

I have a running joke at work "current mock count: 0" in my slack room titles

[Peter]

very nice … i put together a very simple example ktor project for my colleagues, immutable config using config4k, also no DI (using pure functions), also no mocking

[sam]

you don't need mocking

[sam]

I saw a post on twitter the other day, about writing new features without ever running the service. That's what I do, you can be very confident in your code if you unit test it properly, then you QA test it in the "Real world" in your deployed dev env

[sam]

I recently replaced a huge profiles service (I work for grindr), a complete replacement for all profiles endpoints. It was in dropwizard, now it's in ktor. And after replacing 10,000 lines of code, we had like 3 minor bugs after we went into prod. I attribute that to the high quality of tests, which FP (and Kotest!) made possible.

[Peter]

if i pull it over into a public repo, would you be willing to give any feedback? it’s very minimal … might be interesting 🤷‍♂️

[Peter]

whoa.. that’s amazing!

[sam]

always

[Peter]

awesome thank you .. should have it tomorrow, trying to get v0.1 of this jwt library out the door