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 with Report.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 and runner 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)

Instrumentation 1.2.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. It it functionally identical to 1.2.0.

Plugin 1.7.1.0

This release is broken. Please move ahead to 1.7.1.1.

Plugin 1.7.0.0

This release brings compatibility with JUnit 5.7.0 and introduces a few quality-of-life improvements for integrating with projects.

• Become more lenient when test tasks are absent (#226)
• Provide configuration parameters to instrumentation tests, allowing e.g. Extension Auto-Detection to work (#229)
• Automatically exclude JUnit 5 metadata files from causing conflicts during packaging (#233)

Plugin 1.6.2.0

Added

• JUnit 5.6.2

Plugin 1.6.1.0

Added

• Compatibility with Android Gradle Plugin 4.1.x
• JUnit 5.6.1

Changed

• Restricted visibility of internal APIs to prevent them from leaking into consumer code