# Five form routes, tested against a submit click and a server error for the first time

Five form routes had no test for a submit-click or a server-error validation state. Covered for $15.47.

Source: https://codeherder.com/examples/form-validation-coverage-gap/

Examples · Maintenance

Drove all five routes with a real submit click, added a server-error test arm, and extended the browser check so this whole state family has real coverage, not just the blur case.

[Request access →](https://codeherder.com/get-started/#request-access)

Measured from this task's real merge.

A validation probe checked twelve form routes by blurring an empty required field. Five showed no visible error. None of the twelve had ever been checked for a submit-click attempt or a server-error response.

What was asked for

> A blur-triggered validation probe found five form routes with no observable validation-error element, and no route had been tested for a submit-click or a server-error state at all.

Filed by a developer, routed by capability (react).

What the herd did

1. plan
2. code
3. review
4. merge
5. verify
6. done

What it changed

The merge touched 5 files (+448 −28). Among them:

- `app/scripts/check-form-submit-validation.mjs`
- `app/scripts/check-write-arm.mjs`
- `app/scripts/lib/probeFixtures.mjs`
- `scripts/ci-spa-browser.mjs`

What it cost

$15.47 in model spend, 336 agent turns, and 3h 56m from filed to merged. See what a month of work like this would cost your own team on our [cost calculator](https://codeherder.com/calculator).

A probe that checks one interaction leaves every other interaction untested.