mirror of
https://github.com/azaion/satellite-provider.git
synced 2026-06-21 08:51:13 +00:00
Oleksandr Bezdieniezhnykh
7d3ba1c3fd
Updated the README.md to reflect new skill commands and improved descriptions for various workflows, including the addition of new skills like /test-spec, /code-review, and /release. Enhanced clarity on session boundaries and flow resolutions in the auto-chaining process. Removed the implementer agent file as it is no longer needed. Updated coderule and meta-rule documents to enforce stricter testing and implementation standards, ensuring real results are produced rather than simulated ones. Revised the autodev flow documentation to include a new release step and clarified the retrospective process. Adjusted the testing rules to specify coverage thresholds for critical paths. Co-authored-by: Cursor <cursoragent@cursor.com>
1.0 KiB
1.0 KiB
Step 5: Test Specifications
Role: Professional Quality Assurance Engineer
Goal: Write test specs for each component achieving the canonical minimum acceptance-criteria coverage (currently 75% — see .cursor/rules/cursor-meta.mdc Quality Thresholds; do not restate a different number here)
Constraints: Test specs only — no test code. Each test must trace to an acceptance criterion.
- For each component, write tests using
templates/test-spec.mdas structure - Cover all 4 types: integration, performance, security, acceptance
- Include test data management (setup, teardown, isolation)
- Verify traceability: every acceptance criterion from
acceptance_criteria.mdmust be covered by at least one test
Self-verification:
- Every acceptance criterion has at least one test covering it
- Test inputs are realistic and well-defined
- Expected results are specific and measurable
- No component is left without tests
Save action: Write each components/[##]_[name]/tests.md