Codex WeReply Testing Strategy for Rust and Tauri Regressions
Design repeatable Rust service and Tauri checks, starting with a failing case. Use the frontend scripts the project actually provides and document manual interaction checks as needed.
中文Install in Codex
Codex with a WeReply checkout and dependencies for its Rust tests. Verify frontend commands against project scripts.
- Copy the entire pinned `.codex/skills/testing-strategy/` directory to `.agents/skills/testing-strategy/` in the target checkout.
- Open Codex in that checkout and invoke `$testing-strategy` with the example task and desired output.
Example task
Invoke `$testing-strategy` to test a material total from a fixture with three synthetic counts. Ask for a failing test first and compare results before and after the fix.What to check
The regression fixture has a fixed input and expected total. Validation records the initial failure, the passing fix, and any frontend interaction that needs a manual check.
Original SKILL.md on GitHub · Updated
Frequently asked question
What if the frontend has no automated test script?
Check which lint script the project provides and record repeatable manual steps for the affected interaction.