This message was deleted.

We use the BuildCache, even for the Android UI Tests, and we decided it's good enough

I have own scripts. It is huge difference if you run all test (60+ min) and only changed files (few seconds)

@Vojtech Hrdina you have your own scripts to do what?

yes

@Ryan Fioravanti To find modified files and run tests for them instead of running all tests. It is almost same as AffectedModuleDetector. I didn’t know that plugin like this exists…

and @Vojtech Hrdina are you using the gradle build cache in addition? We already use remote build cache so I'm specifically wondering if I'll expect to see value in using both cache and this plugin together

@Ryan Fioravanti No. I experimented with remote cache but I always use clean builds

BuildCache is confiable. Detecting affected tests requires instrumenting and it's a complex thing that could be error prone. Even if done right, the benefits are bigger the less you modularize, and to our use case has a disadvantage: I want to have the full report to compare coverage between commits, if I don't run some tests I can't recalculate how it changed.