NoSuchMethodError pre API 21 about deviceanimationtestrule

[VictorAlbertos]

@johnjohndoe I thin this is the exactly opposite scenario ;)

@twyatt Yes. I think I'm going to document the issue. Thanks for your feedback!

[VictorAlbertos]

Thanks @twyatt for your feedback :)

The problem is that I do not know what would be the best approach to deal with this limitation.

Because this library is meant to be used only for integration testing, so, I think that targeting to api 21 would be more a burden that nothing else. Because doing that, the user of this library is going to need to override the min sdk set by this library ad hoc. Because no one is going to set 21 as the min target xD. But, this requirement is only for the device in which the test are going to be run.

So, what do you think? Any better ideas?

Thanks!

[johnjohndoe]

@twyatt In case you did not see @VictorAlbertos' post on how to bypass the minSdkVersion limitation.

[twyatt]

@VictorAlbertos, from what I can find (Disabling Animations in Espresso for Android Testing and Gist: Disable animations for Espresso tests), it seems that issuing adb commands would be necessary for disabling animations pre API 21? Which is probably outside the scope of what you intended for this project?

That being said, perhaps it would be helpful to have the API limitation documented? When I stumbled on this gem I assumed it worked down to API 16 (based on the build.gradle in the sample app).

[johnjohndoe]

@VictorAlbertos Maybe, I misunderstand the issue.
@twyatt For completeness - this article on "Setting animation scale for Android UI tests" might interest you.

[twyatt]

@johnjohndoe Thanks for linking the article!

Although I'm not sure what is going wrong for me, as neither the method discussed in the article (nor the Gradle plugin mentioned) worked for me. 😢

Even tried issuing adb commands (as mentioned in tasomaniac's comment) without success.

So, I still have yet to find a reliable means of disabling animations for testing (that is compatible pre API 21) without having to manually update settings on every emulator.

[tir38]

May I suggest some sort of fail safe that checks API level before executing this code? Right now, if I run tests on API < 21 i'll just see a crash with no indication of why. It would be nice if I either got a log warning "Hey we were unable to turn off animations", or at the very least just do nothing (i.e. keep animations turned on)

[VictorAlbertos]

@tir38 do you care to submit a PR? Thanks.