new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Vitest · Config reference · all subjects

config/clearmocks

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

clearMocks example configuration

import { defineConfig } from 'vitest/config' export default defineConfig({ test: { clearMocks: false, }, })

clearMocks config option

The clearMocks option is a boolean configuration for Vitest. It defaults to true. When enabled, Vitest automatically calls vi.clearAllMocks() before each test. This clears mock history without affecting mock implementations.

clearMocks pitfall with concurrent tests

The clearMocks option may cause problems with async concurrent tests. If enabled, the completion of one test will clear the mock history for all mocks, including those currently being used by other tests in progress.

Give your agent this brain