<youtube.com/watch?v=80ASd_Kt2tw> seems the record...

# testballoon

[Edoardo Luppi]

youtube.com/watch?v=80ASd_Kt2tw▾

seems the recording is out.
Really good talk btw. Thanks @Oliver.O and @Bernd Prünster.

[Oliver.O]

Oh, cool, thanks for pinging! Happy to hear that you liked it. 😀

[Edoardo Luppi]

It can be used and shared as a testing tutorial, which is pretty nice.

[Oliver.O]

Thanks! Out of curiosity: How did you find that video? It doesn't seem to appear in the Kotlin YT channel.

[Edoardo Luppi]

Kotlin Conf Talks. It now lists available recordings.

[Rafael Costa]

Good job @Oliver.O.
I've felt like junit is dated for kotlin for quite some time, and kotest never really fully felt like the answer (I also use the assertions though).
I'm quite eager to try this one.

[Rafael Costa]

We do also have quite the "unique" testing style in our project where we basically run our whole application without the UI and we mock only the boundaries like network calls and what not.
Seems like it would fit well with the fixtures feature (what we have now is basically a overload of runTest that prepares the fixture in a fresh state for every test and passes that to the lambda as a context parameter).

[Oliver.O]

👍 Just try it. And if there are questions about how your goals could be achieved in the most idiomatic way, don't hesitate to ask them in this channel.

[Edoardo Luppi]

There is an interesting comment on the video. I still don't fall into this use case, but maybe explicitly mentioning it in the readme/docs would be good.

How is it with coverage reports? That was kind of missing.

[Oliver.O]

Interesting. Coverage is independent of the test framework used, so it is just there, to the same degree it is with kotlin.test, as mentioned in the Kover docs:

Collection of code coverage for JVM and Android host tests (JS and native targets are not supported yet).