MavericksView creating uncoverable code

[alisonthemonster]

Hi there! I'm using Mavericks for a few fragments and my project tracks code coverage. I've been testing my fragments using both MockableMavericksViews with screenshot tests and tests with espresso and plain MavericksViews. In both cases I'm not able to achieve passing code coverage because of code from MavericksView. Here's an example:

Is there any way to test these functions, or is there something I'm missing here?

[elihart]

You shouldn't need to test functions that come from other libraries (like mavericks). Seems like your coverage setup needs to be configured to exclude 3rd party code?

[alisonthemonster]

Do you have any examples of how to do this? My googling is just showing how to exclude entire classes.

I did find this issue for jacoco around interfaces with default methods in Kotlin: jacoco/jacoco#905
They talk about byte code so it goes a bit over my head there, but I wonder if its related. They had a fix for default methods with no parameters, and they have an in progress PR for default methods with parameters: jacoco/jacoco#1137