1,533 small questions.

1,533 checks. Where do they go?

The validator in the project behind this series runs 1,533 checks on every build, grouped into families. Each family asks one kind of question, many times over.

Which family do you think runs the most checks?

The families

Tap a bar to see what the family checks. Filter by what part of the project it guards.

Checks that only speak up when something's wrong

Not every check adds to the count. Some are fail-only checks: they print nothing when things are fine and a FAIL line when they aren't. In this validator they cover things like tabs rather than spaces in model files, stray byte-order marks, a measure defined twice, every page in the spec existing, and every visual having a position.

The 'no measure defined twice' check found nothing wrong. Does it add to the 1,533?

Which family catches it?

It started at 710 and grew to 1,533

A project note said the validator ran 710 checks. When asked, the agent reported 1,533, and all of them passing.

Nothing broke. What most likely happened?

Three things to keep

• 1Checks come in families. Each family asks one question, once per thing it applies to.
• 2The pass count leaves out the fail-only check checks, so it understates what's guarded.
• 3The count grows with the spec. A new setting should arrive with its own check.