Me again :joy: I had been struggling to make commo...
# apollo-kotlin
s
Me again 😂 I had been struggling to make common tests work as they were timing out for iosSimulatorArm64 with:
Copy code
UncompletedCoroutinesError: 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?
m
We got
runTest {}
first 😂 !
😂 1
We should certainly deprecate and use another name
Eventually, we should get rework most of the threading to be able to use kotlin's
runTest {}
and also not require
execute()
to be called on the main thread. That'll most likely happen when switching to the new memory model
s
We got
runTest {}
first 😂 !
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
😅 1