Hi Jake, thank you for suggestion, seems good. I only thought about *excluding dependency*, not about flavor-specific *including.*
I'll try it. Btw, what do you think about UiAutomator? As I understand, Square uses Espresso (2x), but it's based on Instrumentation, and tests coupled with Application code too closely, it's a White Box which is bad for Functional testing, I often saw instrumental tests with "hacks" around the views, fragments and so on, users don't look inside the app when they use it :) UiAutomator makes you write tests almost as users would interact with the app + it's system-wide, not only for application process On Thursday, November 27, 2014 10:50:44 PM UTC+3, Jake Wharton wrote: > > Why not just use a flavor-specific dependency on the ones where you do > want it? > On Nov 27, 2014 11:33 AM, "Artem Zinnatullin" <[email protected] > <javascript:>> wrote: > >> Hello everybody. >> >> I have pretty non-standard problem: >> >> App has library as sub-project in dependencies with native part which is >> compiled only for arm (Yandex Map Kit), no x86 version :( >> We have some tests (based on UiAutomator) which we need to execute on the >> CI. >> >> The problem is that we want to use x86 emulators for testing >> (performance) and I need to exclude this sub-project for one special >> "autoTestFlavor" and mock it. >> >> Does anybody know how to remove sub-project from dependencies for one of >> the flavors? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "adt-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
