alicejli
commented
1 year ago Closing this PR as we are still supporting Java 8 and therefore cannot upgrade to use Mockito 5 at this time.
Closed renovate-bot closed 1 year ago
alicejli
commented
1 year ago Closing this PR as we are still supporting Java 8 and therefore cannot upgrade to use Mockito 5 at this time.
forking-renovate[bot]
commented
1 year ago As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will reenable minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
This PR contains the following updates:
4.11.0->5.1.0Release Notes
mockito/mockito
### [`v5.1.0`](https://togithub.com/mockito/mockito/releases/tag/v5.1.0) [Compare Source](https://togithub.com/mockito/mockito/compare/v5.0.0...v5.1.0) *Changelog generated by [Shipkit Changelog Gradle Plugin](https://togithub.com/shipkit/shipkit-changelog)* ##### 5.1.0 - 2023-01-29 - [12 commit(s)](https://togithub.com/mockito/mockito/compare/v5.0.0...v5.1.0) by Andriy Redko, Ashley, Róbert Papp, Stephan Schroevers, Tim te Beek, dependabot\[bot] - Fixes some mistakes and missing details in documentation [(#2889)](https://togithub.com/mockito/mockito/pull/2889) - Bump com.diffplug.spotless from 6.13.0 to 6.14.0 [(#2888)](https://togithub.com/mockito/mockito/pull/2888) - Clean up JDK-8 related code [(#2883)](https://togithub.com/mockito/mockito/pull/2883) - Feat: reified mock overloads [(#2882)](https://togithub.com/mockito/mockito/pull/2882) - Clean up JDK-8 related code [(#2879)](https://togithub.com/mockito/mockito/issues/2879) - Bump assertj-core from 3.24.1 to 3.24.2 [(#2875)](https://togithub.com/mockito/mockito/pull/2875) - Make sure the tests use mock maker with intended member accessor [(#2872)](https://togithub.com/mockito/mockito/pull/2872) - Bump com.diffplug.spotless from 6.12.1 to 6.13.0 [(#2871)](https://togithub.com/mockito/mockito/pull/2871) - Remove broken link from `CONTRIBUTING.md` [(#2870)](https://togithub.com/mockito/mockito/pull/2870) - Update outdated badge 3.x to 5.x [(#2869)](https://togithub.com/mockito/mockito/pull/2869) - Broken link in `CONTRIBUTING.md` [(#2868)](https://togithub.com/mockito/mockito/issues/2868) - Set current version to 5.x in README and highlight changes [(#2867)](https://togithub.com/mockito/mockito/pull/2867) - Annotate `Mockito#{mock,spy}(T... reified)` with `@SafeVarargs` [(#2866)](https://togithub.com/mockito/mockito/pull/2866) - Make sure the tests use mock maker with intended member accessor [(#2855)](https://togithub.com/mockito/mockito/issues/2855) - Improve examples for InOrder [(#2843)](https://togithub.com/mockito/mockito/pull/2843) ### [`v5.0.0`](https://togithub.com/mockito/mockito/releases/tag/v5.0.0) [Compare Source](https://togithub.com/mockito/mockito/compare/v4.11.0...v5.0.0) ### Mockito 5: prepare for future JDK versions For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working. #### Switch the default mockmaker to `mockito-inline` Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass. Massive thanks to community member [@reta](https://togithub.com/reta) who implemented this change. Note: this does not affect `mockito-android` nor testing on Android. ##### When should I still be using the subclass mockmaker? There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker. If you want to use the subclass mockmaker instead, you can use the new `mockito-subclass` artifact (published [on Maven Central](https://search.maven.org/artifact/org.mockito/mockito-subclass) along with all our other artifacts). #### Update the minimum supported Java version to 11 Mockito 4 supports Java 8 and above. Similar to other open source projects, we are moving away from JDK 8 and to newer versions. The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working. Lately we have been running into more and more JDK 8 breakages. Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes [issues with the `SecurityManager`](https://togithub.com/mockito/mockito/issues/2798). Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well. Massive thanks to community member [@reta](https://togithub.com/reta) who implemented this change. ##### What should I do if I still run JDK 8? For JDK 8 and below, you can keep on using Mockito 4. This is similar to if you are using JDK 6, for which you can keep on using Mockito 2. The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal. However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future. #### New `type()` method on `ArgumentMatcher` One of our most used public API's for customizing Mockito is the [`ArgumentMatcher` interface](https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/ArgumentMatcher.html). The interface allows you to define a custom matcher, which you can pass into method arguments to provide more targeted matches. One major shortcoming of the `ArgumentMatcher` was the lack of varargs support. There were many, many issues filed related to varargs and Mockito unable to handle them. Community member [@big-andy-coates](https://togithub.com/big-andy-coates) put in a lot of effort to come up with an appropriate solution, including fully implementing and comparing 2 approaches. Ultimately, we decided that introducing a new `type()` method on `ArgumentMatcher` is the best solution. As a result, it is now possible to update your custom matchers to implement varargs support, if you so desire. Note that `ArgumentMatcher` is still a `@FunctionalInterface` and can therefore still be written as a lambda. Massive thanks to community member [@big-andy-coates](https://togithub.com/big-andy-coates) who implemented this change. ##### What is the effect of this new method? For varargs methods, there was previously a way to only match zero arguments, or two or more arguments, by using the exact number of matchers, i.e. ```java long call(String... args); // Will match calls with exactly zero arguments: when(mock.call()).thenReturn(0L); // Will match calls with exactly two arguments: when(mock.call(any(), any())).thenReturn(0L); ``` But following the pattern to match exactly one argument: ```java when(mock.call(any())).thenReturn(0L); ``` doesn't work, as `any` is "vararg aware", so Mockito matched the `any` against *each element* of the varargs parameter, meaning it will match any number of arguments, i.e. the above would of matched all of these: ```java mock.call(); mock.call("a"); mock.call("a", "b"); ``` With the new `type` method, it's now possible to differentiate matching calls with any exact number of arguments, or to match any number of arguments. ```java // Match any number of arguments: when(mock.call(any(String[].class))).thenReturn(1L); // Match invocations with no arguments: when(mock.call()).thenReturn(1L); // Match invocations with exactly one argument: when(mock.call(any())).thenReturn(1L); // Alternative to match invocations with exactly one argument: when(mock.call(any(String.class))).thenReturn(1L); // Match invocations with exactly two arguments: when(mock.call(any(), any())).thenReturn(1L); ``` Therefore, if you want to match 0 or more arguments, use `any(String[].class)`. If you want to match an exact number of arguments, use `any(String.class)` (and specify as many `any` matchers as arguments you want to match on). In a similar fashion, the behavior of `ArgumentCaptor.forClass` has changed as well. If you want to capture all arguments, use an `ArgumentCaptor` for `String[]`, otherwise `String`: ```java // Will capture 1 string @Captor private ArgumentCaptorConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.