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

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.

changed config option

The changed option has type boolean or string, with default value false. It can be set via CLI with --changed or --changed=HEAD~1. When set to true or with no value, it runs tests only against uncommitted changes (including staged and unstaged). It accepts commit hashes (e.g. --changed 09a9920), branch names (e.g. --changed origin/develop), or relative references (e.g. --changed HEAD~1 for the last commit).

changed with code coverage

When the changed option is used with code coverage, the coverage report will contain only the files that were related to the changes.

changed with forceRerunTriggers

When the changed option is paired with the forceRerunTriggers config option, the whole test suite will run if at least one of the files listed in the forceRerunTriggers list changes. By default, changes to the Vitest config file and package.json will always rerun the whole suite regardless of the changed setting.

Give your agent this brain