How to address the Compose UI negative impacts on the Code Coverage, even after writing tests for it?
I recently migrated my Android pet project from View to Compose UI and at the begining I was excited about all the @Compose
and @Preview
functions but righ away noticed a segnificant drop in the repo’s Code Coverage.