I think it's probably a good idea. https://code.google.com/p/android/issues/detail?id=76249
On Sun, Sep 14, 2014 at 1:52 PM, Artem Zinnatullin < [email protected]> wrote: > I just spend couple hours with Travis CI (connectedAndroidTest on x86 > emulator did not start any test but build was marked as success). > > So, I think it would be better if connectedAndroidTest will fail build if > no tests was started, it's one of the purposes of test tasks, for example > it fails if no device (emulator) was found, but 0 tests is okay... I think > it's wrong philosophy and design > > What's your opinion? > > -- > 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.
