Stylianos Gakis
02/24/2022, 11:35 AMUncompletedCoroutinesError: After waiting for 60000 ms, the test coroutine is not completing
I stumbled upon this by chance and I figured out that there is another runTest
inside apollo-testing? Fortunately this does run now, all tests pass fine by using that runTest instead of the one from Coroutines 1.6.
But that was weeeird, if I didn’t have access to Kotlin slack channel I don’t think I would’ve ever figured this one out. Again, not sure how this could be noted in the docs, but maybe it deserves a spot?
Also if for some reason I also wanted the functionality of the coroutines runTest of passing in a dispatchTimeoutMs
I am now losing that functionality with the apollo version of it right?mbonnin
02/24/2022, 1:26 PMrunTest {}
first 😂 !runTest {}
and also not require execute()
to be called on the main thread. That'll most likely happen when switching to the new memory modelStylianos Gakis
02/25/2022, 7:34 AMWe gotfirst 😂 !runTest {}
Hahaha oh okay, I'm going to redirect my complaints to Elizarov himself then 😂😂 Alright though, I understand now why it is the way it is. Let's hope the new mm stabilizes fast