with one click
code-review-testing
Test authoring guidance
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Test authoring guidance
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Breaking changes
Model visible context
How to run tests using remote executor.
Repo-local guide for testing the Every Code TUI interactively, including live-terminal visibility limits, VT100 snapshot evidence, restart dogfooding, and how to avoid overclaiming visual verification.
| name | code-review-testing |
| description | Test authoring guidance |
For Every Code agent changes, prefer integration tests over unit tests.
Integration tests are under core/suite and use test_codex to set up a test
instance.
Features that change the agent logic MUST add an integration test:
If unit tests are needed, put them in a dedicated test file (*_tests.rs). Avoid test-only functions in the main implementation.
Check whether there are existing helpers to make tests more streamlined and readable.