MINOR: Upgrade mockito test dependencies

[dplavcic]

Changes

• mockito: 4.4.0 -> 4.6.1 (https://github.com/mockito/mockito/releases)
  Most important updates:
  • Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 mockito/mockito#2656
  • Fixes Any way to enable Strict Stubbing when using Mockito.mock() without using @Mock? mockito/mockito#2648 : Add support for customising strictness via @mock annotation and MockSettings Fixes #2648 : Add support for customising strictness via @Mock annotation and MockSettings mockito/mockito#2650

Why is this change needed?

Update 1

According to the Mockito documentation :

Although it is possible to verify a stubbed invocation, usually it's just redundant. Let's say you've stubbed foo.bar(). If your code cares what foo.bar() returns then something else breaks(often before even verify() gets executed). If your code doesn't care what get(0) returns then it should not be stubbed.

While working on the Replace EasyMock and PowerMock with Mockito for StreamsMetricsImplTest I noticed that described behavior wasn't applied when you create a new mock like this.

        final Metrics metrics = mock(Metrics.class);
        when(metrics.metric(metricName)).thenReturn(null);

        ... invoke SUT

        verify(metrics).metric(metricName); // this should be redundant (according to docs)

After further investigation I figured out that described behaviour wasn't implemented untilv4.6.1.

With this change we are now able to mock objects like this:

   Foo explicitStrictMock = mock(Foo.class, withSettings().strictness(Strictness.STRICT_STUBS));

• link to docs: MockSettings.html#strictness

Update 2

It looks like I can accomplish the same thing by using the @RunWith(MockitoJUnitRunner.StrictStubs.class) instead of the @RunWith(MockitoJUnitRunner.class) so mockito dependency version update is not mandatory, but it would be nice to stay up-to-date and use the latest version (it's up to MR reviewer to decide if we are going to merge this now, or just close the MR and update mockito version later).

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[ijuma]

I'm guessing the 4.5.1 to 4.6.0 fix doesn't affect us since we're still on 4.4.0:

Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 mockito/mockito#2656

[ijuma]

LGTM, thanks.