Depends on the definition of easier. If easier is "it won't work with my particular flavour of framework or mocking" then yes, it's a bad idea. If it's inheren

Depends on the definition of easier. If easier is "it won't work with my particular flavour of framework or mocking" then yes, it's a bad idea. If it's inherently untestable for any setup, that's already a smell and needs some sort of attention. If the smell is accompanied by potential to cause catastrophic error or such, I'd rather lean in to changing the code to be more testable even if it feels like an anti-pattern.