I think auto mocking modules is the most horrible trick a testing framework can pull. So because you're too lazy to write modules with a minimum of sane depend

I think auto mocking modules is the most horrible trick a testing framework can pull. So because you're too lazy to write modules with a minimum of sane dependency injection,you hack require (which is not dependency injection) to mock dependencies? This is actually the most awfull anti pattern i've seen in javascript land yet.Unfortunatly, it's becoming the "way to go" for most developpers. Instead of making your modules pluggable and decoupled,you negates everything testing is for,you just dont write testable code.