Jest mocks allow developers to write bad code. Instead of separating concerns with DI, jest mocks overwrite the importing mechanism without any type safety. Also, if you wish to migrate to native node test runner, the mocks lock you into jest.
Use proper mocks with ts mockito and it will force you to write better code.
100%. its a horrible code smell, and AI loves to jest.mock (or vi.mock()). (The most recent blog post on my site covers this as one of the things to look out for in AI generated tests...)
in JS (with Jest/Vitest) it is far too easy to call mock()...
Use proper mocks with ts mockito and it will force you to write better code.
in JS (with Jest/Vitest) it is far too easy to call mock()...
vitest browser mode is really nice too. (new-ish feature, although at this point it isn't exactly new).