They are different packages of the same variant. This means that there is a single connectedCheck task per variants.
When deploying the app and test to a device, the plugin will deploy the most appropriate apk to test to a device alongside the test (of which there is only one). There are clearly some issues with this: - No way to know if you ended up deploying every output. - ABI-based outputs may require test app per ABI. This is definitively something we are going to have to improve later. I've filed https://code.google.com/p/android/issues/detail?id=76723 to track this. On Fri, Sep 26, 2014 at 7:19 AM, Roman Mazur <[email protected]> wrote: > I'm a bit lost with what to do with multiple outputs of test variants... > How do they match application apks? Is it allowed to have abi/density > splits for test variants? > > How generally application apks are supposed to be tested? There should be > a "connected check" task per output? > I'm trying to update our gradle plugin for spoon... And I'm lost :) > > -- > 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. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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.
