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

Storybook · all subjects

testing & test runner

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

Use focused runs while iterating

When iterating on tests, use focused runs for efficiency. Perform a broad pass before handoff when scope is unclear or wide.

Fix failing tests before handoff

Never report completion while tests are failing. All tests must pass before marking work as complete.

When should I use focused runs with the test runner

Use focused runs with the stories input during development to validate the parts you changed quickly. Run all tests by omitting the stories input before final handoff, after broad or refactor changes, or when impact is unclear and you need project-wide verification.

Run story tests after every change

Run the test runner after every component or story change, including creating, modifying, or refactoring components, stories, or their dependencies. It is the only way to run story tests. Never run package.json test scripts like npm run test:stories instead.

Story testing workflow

The story testing workflow is: (1) Make your change, (2) Run the test runner with related stories for focused feedback while iterating, (3) If tests fail, analyze and fix then re-run, (4) Repeat until all tests pass. Do not skip tests, ignore failures, or move on with failing tests.

Run story tests after UI changes

After editing anything that changes how the UI looks, run the story tests using the designated command. Do not use a package.json test script instead.

Never report completion with failing story tests

Do not report completion of work while story tests are failing.

Give your agent this brain