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

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-test and android-instrumentation-test-runner) have been removed. Please upgrade to android-test-core and android-test-runner, respectively. More info on the wiki!