Search for a command to run...
Articles tagged with #vitest
Originally published at recca0120.github.io All tests pass, but the terminal is full of red console.error output. This is common and easy to ignore — the tests passed, after all. But those errors don't appear out of nowhere. Something went wrong; nob...
Originally published at recca0120.github.io How do you test a Node.js service that operates on the filesystem? The obvious approach is to create real files under /tmp, run the tests, then clean up. But that comes with problems: slow I/O, inconsistent...
Originally published at recca0120.github.io The previous posts covered [DI + Fake + in-memory]({{< ref "/post/di-fake-in-memory-testing" >}}) and [sharing Fakes across a monorepo]({{< ref "/post/monorepo-shared-fake-testing" >}}). That approach has o...
Originally published at recca0120.github.io The previous post covered [DI + Fake + in-memory basics]({{< ref "/post/di-fake-in-memory-testing" >}}). This one takes it further, into a scenario most testing tutorials ignore: how frontend, backend, and ...
Originally published at recca0120.github.io The most common testing pattern I see looks like this: test('saves user data', () => { const mockStorage = { set: vi.fn(), get: vi.fn().mockReturnValue(null), }; const service = new UserServic...