Sometimes a user will write a "result = new SomeClass(someMock)" recording, where the called constructor happens to make calls on "someMock". Such indirect recordings are unintended, and can result in confusing exceptions.
Such misuses of the mocking API should be detected, with a helpful exception message shown.
The text was updated successfully, but these errors were encountered:
Sometimes a user will write a "result = new SomeClass(someMock)" recording, where the called constructor happens to make calls on "someMock". Such indirect recordings are unintended, and can result in confusing exceptions.
Such misuses of the mocking API should be detected, with a helpful exception message shown.
The text was updated successfully, but these errors were encountered: