Files
wehub-resource-sync bb5c75ce05
Component Security Validation / Security Audit (push) Has been cancelled
Deploy to Cloudflare Pages / deploy (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:38:58 +08:00

1 line
2.1 KiB
JSON

{"content": "---\nname: test-coverage-loop\ndescription: Adds meaningful tests pass after pass until the suite reaches a target coverage threshold and stays green.\ncategory: engineering\ninterval: 20m\nstop-condition: Coverage meets or exceeds the target (e.g. 90%) with all tests passing and no flaky additions.\ncomponents: [agent:performance-testing/test-automator, command:testing/test-coverage, command:testing/generate-tests]\ntags: [testing, coverage, quality, loop]\n---\n\n# Test Coverage Loop\n\n> **Loop Engineering** — a recurring goal that drives the agent to grow real test coverage incrementally instead of in one risky batch.\n\n## 🎯 Goal\nRaise test coverage toward a defined target by adding **meaningful** tests for the least-covered, highest-risk code first — never gaming the metric with empty assertions.\n\n## ⏱️ Schedule\nSuggested interval: `20m`.\n\n## ▶️ Run it\n```\n/loop 20m \"Measure current test coverage. Pick the lowest-covered, highest-risk module and add real, behavior-focused tests for it. Re-run the suite. Continue until coverage is at least 90% with everything passing.\"\n```\n\n## 🔁 Iteration steps\n1. **Perceive** — run the coverage report and rank uncovered code by risk.\n2. **Reason** — identify branches, error paths and edge cases that lack tests.\n3. **Plan** — choose one module/area to cover this pass.\n4. **Act** — generate tests with `test-automator` + `/generate-tests`.\n5. **Observe** — re-run `/test-coverage`; if the suite is green and coverage rose, continue; if flaky, fix before moving on.\n\n## 🛑 Stopping condition\nCoverage ≥ target, full suite passes, and no newly-added test is flaky.\n\n## 🧩 Referenced components\n- `agent:performance-testing/test-automator` — authors the tests.\n- `command:testing/test-coverage` — measures progress each pass.\n- `command:testing/generate-tests` — scaffolds new test cases.\n\n## 💡 Example\nStarting at 61%, the loop targets the untested error branches of the payment module first, climbing a few points per pass until it crosses 90% with a green suite.\n"}