not sure where to post this, but when you use `runBlocking {}` in junit tests and you have `assertEq...

# announcements

[Dias]

not sure where to post this, but when you use runBlocking {} in junit tests and you have assertEquals() as the last call (or any kotlin test assertion) it doesn't work, because tests should have Unit return type, but since asserEquals returns stuff, junit doesn't pick up the test. What can I do? I can just put Unit in the end of the call, but it does't look good

[Tsvetozar Bonev]

Why are you asserting inside of the runBlocking?

[Dias]

I treat whole body test as a block

[Tsvetozar Bonev]

what are you running asynchronously?

[Dias]

stuff

[Tsvetozar Bonev]

launch { } doesn't return anything

[Tsvetozar Bonev]

I think that might help you

[Dias]

but I need it to finish before test executes

[Dias]

having val x = runBlocking {} within the test body doesn't look good either

[Tsvetozar Bonev]

I can't think of a way to get around the ugliness that runBlocking causes in such a test 😄

[Pavlo Liapota]

write runBlocking<Unit> { }? 🙂

[Dias]

that works, thanks! I knew that would be easy solution

[Dias]

but the bit I am missing is: I tried doing thing like

fun test(): Unit = runBlocking {}

[Dias]

but it complained about expected type mismatch

[Dias]

why doesn't it do it here?

[karelpeeters]

I think the behavior you're looking for is called "forward inference", and Kotlin doesn't have it simple smile