3 ms·
"Redesign your code so it only interacts with such code at the edges." yeah, and what if you don't have time to do this? sometimes mocks are appropriate becau
by pswenson 12y ago
"Redesign your code so it only interacts with such code at the edges."
yeah, and what if you don't have time to do this? sometimes mocks are appropriate because of schedules and other priorities. Much better to mock than to not write tests because mocking is not pure.
- eropple 12y agoQuit? Before it makes you quit? If your schedules and other priorities are against fixing broken code, I'd be leery of your organization's long-term health. If you're in for the long haul--and at my current gig I certainly am--then eliminating bad code (and any code as tightly coupled as what you describe) is the only sane option. Because it'll kill you eventually.