eo-test

What problem does it solve?

Provides a disciplined, repeatable way to write, run, and document tests for implemented changes so that feature acceptance is verified without touching production business code or silently patching failures.

Core Features & Use Cases

• Test authoring: Write and optimize unit and integration tests strictly within test directories based on change.md acceptance criteria.
• Execution & evidence: Run project test commands, collect outputs, exit codes, and logs as execution evidence for each scenario.
• Structured reporting: Produce a standardized eo-doc/dev/<module-name>/changes/<change-id>/test.md with summary metrics, failure analysis, and reproduction evidence.
• Safety guardrails: Enforce a strict prohibition on modifying non-test business code and require recording of any discovered bugs in the report rather than fixing them inline.

Quick Start

Run eo-test for module my-module and change 001-add-feature to write and run tests against eo-doc/dev/my-module/changes/001-add-feature/change.md and produce eo-doc/dev/my-module/changes/001-add-feature/test.md.