mockito

Replace the dependency on the test package with a dependency on the new test_api package. This dramatically reduces mockito's transitive dependencies.

This bump can result in runtime errors when coupled with a version of the test package older than 1.4.0.

Deprecate the typed API; instead of wrapping other Mockito API calls, like any, argThat, captureAny, and captureArgThat, with a call to typed, the regular API calls are to be used by themselves. Passing any and captureAny as named arguments must be replaced with anyNamed() and captureAnyNamed, respectively. Passing argThat and captureThat as named arguments must include the named parameter.

Introduce a backward-and-forward compatible API to help users migrate to Mockito 3. See more details in the upgrading-to-mockito-3 doc.

thenReturn now throws an ArgumentError if either a Future or Stream is provided. thenReturn calls with futures and streams should be changed to thenAnswer. See the README for more information.

Support stubbing of void methods in Dart 2.

thenReturn and thenAnswer now support generics and infer the correct types from the when call.

Completely remove the mirrors implementation of Mockito (mirrors.dart).

Fix compatibility with new noSuchMethod Forwarding feature of Dart 2. This is thankfully a mostly backwards-compatible change. This means that this version of Mockito should continue to work:

• with Dart >=2.0.0-dev.16.0,
• with Dart 2 runtime semantics (i.e. with dart --preview-dart-2, or with Flutter Beta 3), and
• with the new noSuchMethod Forwarding feature, when it lands in CFE, and when it lands in DDC.

This change, when combined with noSuchMethod Forwarding, will break a few code paths which do not seem to be frequently used. Two examples:

class A {
  int fn(int a, [int b]) => 7;
}
class MockA extends Mock implements A {}

var a = new MockA();
when(a.fn(typed(any), typed(any))).thenReturn(0);
print(a.fn(1));

This used to print null, because only one argument was passed, which did not match the two-argument stub. Now it will print 0, as the real call contains a value for both the required argument, and the optional argument.

a.fn(1);
a.fn(2, 3);
print(verify(a.fn(typed(captureAny), typed(captureAny))).captured);

This used to print [2, 3], because only the second call matched the verify call. Now, it will print [1, null, 2, 3], as both real calls contain a value for both the required argument, and the optional argument.

Upgrade package dependencies.

Throw an exception when attempting to stub a method on a Mock object that already exists.