Codex Agentskel Test Design with Concrete Inputs and Assertions
Plan tests with clear scenarios, expected results and explicitly identified synthetic fixtures.
中文Install in Codex
Open a workspace using Agentskel test guidance in Codex with its affected business rule and current framework.
- Review `.agents/skills/test-engineer/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/test-engineer/` in your project and save the reviewed file as `.agents/skills/test-engineer/SKILL.md`.
- Start Codex from that project's root, then type `$test-engineer` and select the matching skill.
Example task
Draft a web unit test for this illustrative label-formatting rule.
{"framework":"Vitest","input":" River ","action":"formatLabel","expected":"River","fixture":"synthetic"}What to check
Use `Vitest` to test how `formatLabel` handles whitespace. Assert `result=River` and name the test for the scenario and outcome.
Original SKILL.md on GitHub · Updated
Frequently asked question
Can I reuse the illustrative fixture as production data?
Label synthetic and test data explicitly. Carry test results in separate records from production.