hello, Andy!

how can I help you today?

though if your question is "what will the 'tasty treat' be for Android Q", I have no idea

hey mark, is there a way to debug a unit test in android studio now? I switched to using kotlin on android studio 3.3 and it doesnt hit any breakpoints though it does throw an error indicating that the function was run

unit tests have been acting strange for a year or so

yeah desserts that start with Q please

technically, they don't have to be desserts, but we're short on any sort of foods that being with Q...

in terms of the unit tests, I couldn't get them to run reliably in Android Studio for much of the latter half of last year, let alone get them working in a debugger

ok thanks

I settled for running the Gradle tasks from the command line

ok i'll check that out

all the android codenames have been sweets though

I haven't worked with unit tests much in AS 3.3 yet, so I can't comment on any new and exciting problems

haha

"tasty treats" is the official phrase for the scope of the Android release code names

but Q is gonna be a problem

ah i didnt know that

i ran through the gamut and noticed they were all sweets so

quiche

tasty, but "treat" would be a stretch, and awfully similar to pie

qaramel lol

back to android, um have you run into "java.lang.AssertionError: Not completed (latch = 1, values = 0, errors = 0, completions = 0, timeout!

sounds like a CountDownLatch didn't get released

is this coming directly from your test code? your app code? framework code? something else?

google says that happens when running a test on different threads and the observer didnt have time to receive the emission? This is thrown from my unit test

what sort of observer?

rxjava 2 observer

I don't recall getting that with RxJava 2 unit tests, though there are a variety of ways of implementing such tests, so perhaps mine used something else

cool

thank you