![]() Instrumentation tests still depend on JUnit 4 and the AndroidJUnitRunner. Some Rules may be supported with the JUnit 5 migration support, but if not you will have to wait until the Rules are rewritten as extensions or not use the Rules at all. However if you use JUnit 4 Rules in your tests, there is limited support in JUnit 5 as they are meant to be replaced with extensions. JUnit 5 has also been released recently, and with the help of this plugin you can use it for unit testing in Android Studio. Some older libraries and code may have some problems with this build stage. The Jack tool chain has been replaced with the desugar tranformation process to support Java 8. Some ideas floated around to support older API version, are to have min API version flavors or do Build.VERSION checks for the API version in the code to provide alternative code paths. Since devices running Nougat or Oreo are still in the minority, supporting older versions will continue to be an issue for a while if you want to use Java 8. Just be aware that many of the Java 8 language features will only be available if the minSkdVersion is 24. Finally I can say goodbye to RetroLambda (although many thanks to the authors for this very useful library). ![]() Java 8 was released back in 2014, and with Android Studio 3.0 it is finally supported in Android. Hopefully this will be useful for anyone thinking of upgrading from Android Studio 2.x. ![]() ![]() This is just some initial comments on using some common and new Android tools and libraries with the 3.0 version of Android Studio and the associated Android Gradle plugin. ![]() I have been using Android Studio 3.0 since since the alpha versions, and it is good to see it finally released. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |