azaion/gps-denied-onboard

Fork 0

mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-23 03:01:12 +00:00

Files

T

Oleksandr Bezdieniezhnykh 1f634c2604

ci/woodpecker/push/02-build-push Pipeline failed

Details

Update demo replay validation and testing documentation

- 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.

2026-06-20 11:24:43 +03:00

1.5 KiB

Raw Blame History

Mode: cycle-update

A scoped refresh of existing test-spec artifacts against the current feature cycle's completed tasks. Used by existing-code flow's per-cycle sync step.

Inputs

The list of task spec files in _docs/02_tasks/done/ implemented in the current cycle
_docs/03_implementation/implementation_report_{feature_slug}_cycle{N}.md

Phases that run

Skip Phase 1 (input data analysis)
Skip Phase 4 (script generation)
Run a narrowed Phase 2 and Phase 3 per the rules below

Narrowed rules

For each new AC in the cycle's task specs, check traceability-matrix.md. If not covered, append one row.
For each new component surface exposed in the cycle (new endpoint, event, DTO field — detectable from task Scope and from diffs against module-layout.md), append scenarios to the relevant blackbox-tests.md / performance-tests.md / security-tests.md / resilience-tests.md / resource-limit-tests.md category. Reuse the existing test template shapes.
For each NFR declared in a cycle task spec, propagate it to the matching spec file. If the NFR conflicts with an existing spec entry, present via the Choose format.
Do NOT rewrite unaffected sections. Preserve existing traceability IDs.
Save only the files that changed, update traceability-matrix.md last.

Save action

Save only the changed test artifact files under TESTS_OUTPUT_DIR. Update traceability-matrix.md last, after all per-category files are written.

1.5 KiB Raw Blame History