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/allowonly

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

allowOnly CLI flags

The allowOnly option can be set via CLI using --allowOnly to enable it or --allowOnly=false to disable it.

allowOnly enabled behavior

When allowOnly is enabled (true), Vitest will not fail the test suite if tests marked with the only flag are detected, even in CI environments.

allowOnly disabled behavior

When allowOnly is disabled (false), Vitest will fail the test suite if tests marked with the only flag are detected, even in local development environments.

allowOnly config example

To enable allowOnly in vitest.config.js: import { defineConfig } from 'vitest/config' export default defineConfig({ test: { allowOnly: true, }, })

allowOnly config option

The allowOnly configuration option controls whether Vitest allows tests marked with the only flag. It is a boolean option with a default value of !process.env.CI. This means by default, the only flag is allowed in local development environments but not in CI environments. The option can be set via CLI using --allowOnly or --allowOnly=false.

allowOnly type and default

The allowOnly option has type boolean with default value !process.env.CI (true when not in CI, false when in CI).

Give your agent this brain