Releases: mannodermaus/android-junit-framework
Gradle Plugin 1.6.0.0
This release of the android-junit5 Gradle Plugin brings compatibility with JUnit 5.6.0.
An important note for upgraders: From this point onwards, android-junit5 requires at least Android Gradle Plugin 3.5.0 and Gradle 6.1.1. This is a substantial upgrade in minimum requirements which hopefully allows for trimming down old workarounds on antiquated versions.
Instrumentation 1.2.0
This release of the instrumentation test libraries brings some QOL improvements for working with Android tests using JUnit 5!
Added
- Conditional test execution: Control the execution of tests dynamically; constrain tests to run only when certain conditions are met. This includes support for most of the annotations provided by the main JUnit Jupier API, as well as some custom ones specifically for Android development! Check out the wiki for more information.
Fixed
- Execution of individual instrumentation tests works now
- Reporting of instrumentation tests uses improved naming schemes, preventing "mangled test names", esp. for parameterized and other non-default tests
Removed
- The source for the old & deprecated instrumentation artifacts (
android-instrumentation-testandandroid-instrumentation-test-runner) have been removed. Please upgrade toandroid-test-coreandandroid-test-runner, respectively. More info on the wiki!
Gradle Plugin 1.5.2.0
This release of the android-junit5 Gradle Plugin brings compatibility with JUnit 5.5.2.
Gradle Plugin 1.5.1.0
This release of the android-junit5 Gradle Plugin brings compatibility with JUnit 5.5.1.
Fixed
- Compatibility for the latest iterations of AGP 3.6.x (#180)
Gradle Plugin 1.5.0.0
This release of the android-junit5 Gradle Plugin brings compatibility with JUnit 5.5.0.
Added
- Integrity checks for users including instrumentation tests into their project. An error will be thrown on incomplete setup of the instrumentation test environment. To disable the check, use the
junitPlatform.instrumentationTests.integrityCheckEnabledAPI - Added Gradle tasks to generate resource files for filter configurations in instrumentation tests (support
@Tagfilters in instrumentation tests)
Changed
- Use Dokka for platform-agnostic generation of documentation files
Removed
- Marked
junitPlatform.instrumentationTests.enabledandjunitPlatform.instrumentationTests.versionas deprecated, as they don't do anything anymore - they are scheduled for removal in 1.6.0.0
Instrumentation 1.1.0
This version of the instrumentation libraries allows filtering support with @Tag for instrumentation tests! 🎉
Added
- Added support for
@Tagfiltering in androidTest methods & classes; this requires using Gradle Plugin1.5.0.0or newer to work!
Changed
- Replaced
RunnerBuilderimplementation for JUnit 5 to be less dependent on theJUnitPlatformRunner
Gradle Plugin 1.4.2.1
This version of the JUnit 5 plugin for Android fixes the compatibility with the latest versions of the Android Gradle Plugin, including the preview releases for 3.5 and 3.6.
Gradle Plugin 1.4.2.0
This release brings the compatibility to JUnit 5.4.2.
Instrumentation 1.0.0
The new instrumentation libraries are here! 🎉🎉🎉
dependencies {
androidTestImplementation "de.mannodermaus.junit5:android-test-core:1.0.0"
androidTestRuntimeOnly "de.mannodermaus.junit5:android-test-runner:1.0.0"
}(More info regarding the setup can be found in the README, and shortly on the Wiki. Also, please allow some time for the new artifacts to become available on JCenter - their submission is currently pending.)
Getting to know the new libraries
The integration of JUnit 5 into Android instrumentation tests has never been easier. We introduce a new core library, and a revamped runner to execute the new tests on supported devices!
-
The best news upfront: The high
minSdkVersionrequirement has been removed. Of course, JUnit 5 tests will still only run on devices with supported software (i.e. Android 8.0/API 26 or higher). However, you won't need to create custom flavors to host your tests any longer. If you execute a test suite containing JUnit 5 tests on an older device, the test runner will simply ignore the new tests. -
@ActivityTestis deprecated. With Google's push towards a unified testing API, the new JUnit 5 core library for Android tests has also migrated to the newActivityScenarioAPI. There is an extension which you can drop into your classes, granting access to an underlying scenario, very much like theActivityScenarioRulewould do. -
The "old" instrumentation library is now deprecated. Please use
android-test-corefrom now on!
Gradle Plugin 1.4.1.0
This release brings the compatibility up to JUnit 5.4.1.