Releases: mannodermaus/android-junit5
Plugin 1.9.2.0
This release of the Gradle plugin brings compatibility with JUnit 5.9.2.
Since this version is released very shortly after its predecessor, please keep in mind that version's repercussions as well when upgrading your plugin: From this version onwards, the minimum supported version of the Android Gradle Plugin is 7.0. Likewise, the minimum supported version of Gradle is 7.0. If you can't update to AGP 7.0 or newer yet, please stay on the 1.8.x.y plugin line.
Plugin 1.9.1.0
This release of the Gradle plugin brings compatibility with JUnit 5.9.1.
Since this version is released very shortly after its predecessor, please keep in mind that version's repercussions as well when upgrading your plugin: From this version onwards, the minimum supported version of the Android Gradle Plugin is 7.0. Likewise, the minimum supported version of Gradle is 7.0. If you can't update to AGP 7.0 or newer yet, please stay on the 1.8.x.y plugin line.
Plugin 1.9.0.0
This release of the Gradle plugin brings compatibility with JUnit 5.9.0, as well as several internal refactorings and improvements. From this version onwards, the minimum supported version of the Android Gradle Plugin is 7.0. Likewise, the minimum supported version of Gradle is 7.0. If you can't update to AGP 7.0 or newer yet, please stay on the previous release.
- JUnit 5.9.0
- Add support for Android Gradle Plugin 8.x.y
- Raise minimum supported versions for AGP and Gradle to 7.0.x and 7.0, respectively
- Refactor implementation to mostly use new Variant API from Android Gradle Plugin
- Remove integrity check and the
integrityCheckEnabled
flag for instrumentation tests (they are auto-configured if junit-jupiter-api is found on theandroidTest
classpath) - Use the correct Kotlin source directory set on AGP 7 (@Goooler, #279)
- Recommend new plugin DSL for configuration over legacy DSL
- Work around breaking binary change for PackagingOptions in AGP 8.x
Plugin 1.8.2.1
Plugin 1.8.2.0
This release of the Gradle plugin brings compatibility with JUnit 5.8.2.
Plugin 1.8.1.0
This release of the Gradle plugin brings compatibility with JUnit 5.8.1 and some internal restructuring around deprecated APIs to preent warnings on Gradle 7.0 and above.
- JUnit 5.8.1
- Replaced deprecated method
Report.setEnabled
withReport.required.set
to remove deprecation warnings in Gradle 7+ (CC @gmarques33, #260)
Plugin 1.8.0.0
This release of the Gradle plugin brings compatibility with JUnit 5.8.0. From this point onwards, the minimum supported Android Gradle Plugin is 4.0. If you need to stay on the 3.x line, please refrain from updating to this version of android-junit5
. In any case, please read through the changelog carefully, especially the "Removed" section. Going forward, you'll have to specify the full ID of the plugin instead of the android-junit5
shortcut.
Added
- JUnit 5.8.0
- New Plugin Marker artifact facilitating usage of the plugin through the
plugins {}
DSL
Changed
- The plugin no longer requires users to apply an Android plugin first - ordering can be arbitrary
Removed
- Support for Android Gradle Plugins 3.x
- Support for the deprecated com.android.feature plugin, which was removed in Android Gradle Plugin 4.x
- The shorthand version for applying the plugin through the
android-junit5
ID has been removed. Going forward, please apply the Android JUnit 5 plugin through the long form:de.mannodermaus.android-junit5
Instrumentation 1.3.0
This release of the instrumentation libraries requires JUnit 5.8.0 or newer. Please check your dependency declarations!
Changed
- Restructured and converted internal code of
core
andrunner
modules to 100% Kotlin
Fixed
- Running an individual test method with parameters will properly execute that test, even from the IDE (#199)
(Note: Due to limitations with Android's instrumentation, this test would be reported without its parameters in the report) - Running an individual test method with @DisplayName will properly execute that test, even from the IDE (#207)
(Note: Due to limitations with Android's instrumentation, this test would be reported with its technical method name instead of the display name when executed in isolation)
Instrumentation 1.2.2
This release of the instrumentation test libraries fixes an issue with how the last version's metadata was deployed to Maven Central. Some missing dependencies were causing instrumentation tests to not be picked up at runtime. This is now resolved!
Fixed
- Include missing transitive runtime-only dependencies in generated POMs (side-effect of moving to a different deployment script) #241
Plugin 1.7.1.1
This release of the Android JUnit 5 is the first version to be released on Maven Central! Going forward, new versions will no longer be published to JCenter.
Added
- JUnit 5.7.1
Changed
- Move location of "junitPlatform" extension to Project
- Migrate Jacoco task integration to new lazy Gradle API
- Migrate instrumentation test integration task to new lazy TaskProvider API
Fixed
Removed
- Remove workaround for KotlinJvmOptions (not needed anymore)