4 ms·
Mocks make it easy to record and assert on method invocations. Additionally spys (instance mocks) are really useful when you need to forward to the real method
by krackers 10mo ago
Mocks make it easy to record and assert on method invocations. Additionally spys (instance mocks) are really useful when you need to forward to the real method or rely on some state.
At the moment I can't see anything Mokckito gives that you technically couldn't implement yourself via subclassing and overriding, but it'd be a lot of boilerplate to proxy things and record the arguments.
- sunnybeetroot 10mo agoSubclasing and overriding is not a good idea. There is no compilation failure if you forget to override a function which can lead to flakey tests at best and prod data impact at worst.
- wmichelin 10mo agoyour test environment should not have the credentials to write to prod data. yiiiiikes!
- sunnybeetroot 10mo agoCredentials end up existing in prod because the person used Mochito and didn’t override the function for providing credentials :’c
- senbrow 10mo agoCredentials should only be provided at the application root, which is going to be a different root for a test harness. Mockito shouldn't change whether or not this is possible; the code shouldn't have the prod creds (or any external resource references) hard coded in the compiled bytecode.
- sunnybeetroot 10mo agoI totally agree, I’m being tongue in cheek, but given how poor some codebases can be, the more precautions the better ie compilation failures on non-mocked functions.