pajatopmr07/20/2020, 5:35 AM
gildor07/20/2020, 5:47 AM
pajatopmr07/20/2020, 6:32 AM
gildor07/20/2020, 6:52 AM
but still not ready for prime-timeWhy?
streetsofboston07/20/2020, 12:03 PM
gildor07/20/2020, 3:43 PM
pajatopmr07/24/2020, 6:17 AM
, but with 1.3.72 these workarounds no longer work. With IntelliJ the JetBrains code coverage tool is way better than Jacoco. I'm guessing this is the case for unit testing (off device) with Android Studio as well. btw, the preferred approach by the Jacoco devs in dealing with Kotlin is to use a filter for dealing with generated code like lateinit. This has me concerned that the Jacoco project is unlikely to treat Kotlin as a first class citizen. It might be time to give up on Jacoco and find another solution. Thoughts?
gildor07/24/2020, 8:12 AM
pajatopmr07/24/2020, 9:03 AM
I saw results that used to be better (pre-compose). I will continue to analyze this code but, as you might imagine, it is very heavy going. I've no intention on convincing any Kotlin team to do anything. A community solution is the only solution I foresee. I see KMP as needing code coverage for all targets, preferably a common solution. Right now there are a few sort-of solutions in the JVM space (Jacoco and IntelliJ), some in the native space (gcov and whatever LLVM uses) and I don't know what in the JS or WASM space. Long term, I don't think this works well. And I have no clue what shape a long term solution takes. For me, it is becoming an itch that I might just have to scratch sooner than later.