mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-21 09:01:14 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
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