Codex Perigon CLI Regression Tests with Local HTTP Stubs
Design focused xUnit v3 regression tests for Perigon CLI using local HTTP stubs and assertions on observable command output.
中文Install in Codex
Open the Perigon CLI .NET workspace in Codex with the expected command behavior and existing test location.
- Review `.agents/skills/test/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/test/` in your project and save the reviewed file as `.agents/skills/test/SKILL.md`.
- Start Codex from that project's root, then type `$test` and select the matching skill.
Example task
Design a Perigon CLI result-display regression case that never contacts the live service.
{"command":"list","stubStatus":200,"responseItems":0,"displayText":"No records"}What to check
Propose an xUnit v3 case under `tests/StudioMod.Tests/Commands`. Return 200 and no items from the local stub and assert that the output displays `No records`.
Original SKILL.md on GitHub · Updated
Frequently asked question
How much validation is needed for a small command-output change?
Start with the targeted regression case. Expand validation when the change spans additional layers.