caliber-testing

Standardizing Vitest tests requires placing files in a __tests__ directory adjacent to source code and naming them with the [module].test.ts pattern to ensure consistent organization and discoverability.

To prevent environment variable pollution in Vitest, wrap any environment changes using beforeEach and afterEach hooks so variables are reset after each test run.

The best way to mock modules in Vitest is using hoisted vi.mock() at the top of files and relying on the global mock configured in src/test/setup.js to avoid bespoke mock definitions.

ES module imports fail in Vitest when missing file extensions; standardizing imports by explicitly including the .js extension resolves path resolution issues during test execution.

Yes, Caliber testing works without bespoke mocks by relying on a global LLM mock established in src/test/setup.js, ensuring consistent behavior across your test suite without manual setup.