Hello guys anyone here knows if there’s a way to ...

# coroutines

[vitrox1]

Hello guys anyone here knows if there’s a way to test coroutines with espresso I mean is not detecting the async process as usually espresso does, so is going forward into the testing code without await ?

[louiscad]

@vitrox1 I'd use

runBlocking {
    ...//your test with async code that you await
}

from kotlinx.coroutines

[vitrox1]

thanks i’ll try it then!

[streetsofboston]

@vitrox1 See here https://kotlinlang.slack.com/archives/C1CFAFJSK/p1514587005000095

[streetsofboston]

I used this to not use runBlocking and have my tests finish quickly

[louiscad]

@streetsofboston Not using runBlocking or similar means any exception in your tests that happens async or after any suspension point don't get caught silently! ❌ 🚨

[streetsofboston]

That’s true. But sometimes you can’t have your test-suite take seconds go run, especially when using delay and such.

I wonder if it is possible to catch exceptions when not using runBlocking when creating your own CoroutineContext.

[louiscad]

@streetsofboston The long tests are not meant to be run on each build or each modification. Also, IIRC, there's test duration hint annotations for Android (which seems to be what you're using)

[louiscad]

Also, if you test your code, it's that you have doubts 🤔 🧌
More seriously, it's important to make sure your tests are right and don't pass silently ignoring unexpected failures. Flaky tests are worst than no tests

[streetsofboston]

Yes, you’re right that you can annotate your tests, but for some things you’d like your tests to run as fast as possible, much like when your code under test encounters Rx Java. I’ll look if I can modify my TestCoroutineContext to catch any thrown exception and have it report it.

[louiscad]

@streetsofboston FYI, runBlocking { … } has seen performance improvements in a very recent update (0.20 IIRC)