Have a test written using Kotlin Test (<https://gi...

# coroutines

[napperley]

Have a test written using Kotlin Test (https://github.com/kotlintest/kotlintest) that uses Coroutines which guarantees the execution order, but appear to have encountered a "dirty read" scenario where the HTTP response status returned is all over the place (returns 0, but if the read is done in a while loop then 200 is returned). Are there any techniques that can be used with Coroutines that will make it easier to detect "dirty read" scenarios?