tree 6002588f74434bdfcf4e6e80f63cc321def94a1d
parent 10cd1fc26bc21cda620853707ef160059a2f3110
author srawlins <srawlins@google.com> 1617816510 -0400
committer Sam Rawlins <sam.rawlins@gmail.com> 1618254249 -0700

Allow calling methods with void return types w/o stubbing.

Having to stub a `void` function before calling it confuses developers. They write `when(mock.methodReturnsVoid(any)).thenReturn(` and then might really have to scratch their heads about what makes sense to return from a mock of a void function. And all this just to satisfy a requirement to have sane return values, which I think just doesn't apply to void (and `Future<void>` and `Future<void>?`) functions.

This CL changes the logic that determines whether a method (or field, or setter) needs to be overridden. It now includes the case for these void-ish methods.

Fixes https://github.com/dart-lang/mockito/issues/367

PiperOrigin-RevId: 367247168