# Green

Green is the state of a check or pipeline that reports success. Nicholas Hopper defines in writing what does not count as green, because a pipeline run by AI coding agents can report success without having tested anything.

- **Published:** November 17, 2026
- **Updated:** November 17, 2026

## A pipeline that was green without testing

On Vibecode City, the deploy gate never ran the unit test suite. Nine tests broke over time while continuous integration stayed green. Nicholas Hopper repaired the nine and added the suite to the gate.

The same project's smoke tests ran as one chain of commands joined with `&&`. The first failing smoke test stopped every test after it from running, so one break hid sixteen others. Hopper replaced the chain with a runner that executes every smoke test and reports all results. The first full run was 20 of 21 passing.

## What Nicholas Hopper does not accept as green

At APX Stream, Hopper wrote these into the skill that agents follow when delivering work to the main branch:

- A gate that skipped tests it was expected to run is not green.
- A test of mocked wiring is not proof that a real integration works.
- A gate that leaves generated output modified is not green.
- A gate's exit code may not be hidden behind `grep`, `tail` or `tee`.
- A user-interface test that injects its own fixtures is not proof that the real backend path exists.

## Checks that pass while the product is broken

On a client project, a performance change passed the type checker, the linter and the production export, and was still broken in the browser. Hopper found it only by loading the built bundle in a headless browser.

## Related skills

- [Claude Code](https://nicholashopper.com/skills/claude-code.md)
- Codex
- GitHub Actions
- Playwright

## Related projects

- [Vibecode City](https://nicholashopper.com/projects/vibecode-city.md)

---

Canonical page: https://nicholashopper.com/notes/green  
Last updated: 2026-11-17  
Index of all pages: https://nicholashopper.com/llms.txt
