+1 for the same reasons. On Wed, 11 Jan 2023 at 20:14, David Capwell <dcapw...@apple.com> wrote:
> +1. We already use mockito. Also that library is basically empty, its > just defining configs for extensions (see > https://github.com/mockito/mockito/tree/main/subprojects/inline/src/main/resources/mockito-extensions > ) > > On Jan 11, 2023, at 12:02 PM, Miklosovic, Stefan < > stefan.mikloso...@netapp.com> wrote: > > Hi list, > > the test for (1) is using mockito-inline dependency for mocking static > methods as mockito-core is not able to do that on its own. mockito-inline > was not part of our test dependencies prior this work. I want to ask if we > are all OK with being able to mock static methods from now on with the help > of this library. > > Please tell me if we are mocking static methods already by some other (to > me yet unknown) mean so we do not include this unnecessarily. > > G:A:V is org.mockito:mockito-inline:4.7.0 > > (1) https://issues.apache.org/jira/browse/CASSANDRA-14361 > > Thanks > > >
