alt Hacker NewsThe whole mocks, fakes and the rest were always a terrible idea. Although people didn't realize it st the time, they were a band-aid to try to make poorly architected code testable.
90% of the time, needing to use a mock is one of the clearest code warning smells you have of there being an issue in the design your code.
It took a while, but the industry seems to be finally (although slowly) coming to this realization. And hopefully with it almost all of this can go away.
Replies
danparsonson • yesterday at 11:24 PM
How do you substitute for dependencies that you're not testing, or that you want to deliberately break?
➕ show 2 replies
fud101 • today at 3:19 AM
Ok, can someone explain this to someone with double digit iq? Is it validating the adapter idea or something else?
I agree. Tests relying on mocks rarely uncover or prevent issues. They also typically make it harder to make changes. Very bad idea that should have been left behind years ago.