mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-23 06:11:12 +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.
54 lines
2.3 KiB
Markdown
54 lines
2.3 KiB
Markdown
# Phase 6: Final Verification
|
|
|
|
**Role**: QA engineer
|
|
**Goal**: Run all tests end-to-end, compare final metrics against baseline, and confirm the refactoring succeeded
|
|
**Constraints**: No code changes. If failures are found, go back to the appropriate phase (4/5) to fix before retrying.
|
|
|
|
**Skip condition**: If the run name contains `testability`, skip Phase 6 entirely — no test suite exists yet to verify against. Proceed directly to Phase 7.
|
|
|
|
## 6a. Run Full Test Suite
|
|
|
|
1. Run unit tests, integration tests, and blackbox tests
|
|
2. Run acceptance tests derived from `acceptance_criteria.md`
|
|
3. Record pass/fail counts and any failures
|
|
|
|
If any test fails:
|
|
- Determine whether the failure is a test issue (→ return to Phase 5) or a code issue (→ return to Phase 4)
|
|
- Do NOT proceed until all tests pass
|
|
|
|
## 6b. Capture Final Metrics
|
|
|
|
Re-measure all metrics from Phase 0 baseline using the same tools:
|
|
|
|
| Metric Category | What to Capture |
|
|
|----------------|-----------------|
|
|
| **Coverage** | Overall, unit, blackbox, critical paths |
|
|
| **Complexity** | Cyclomatic complexity (avg + top 5 functions), LOC, tech debt ratio |
|
|
| **Code Smells** | Total, critical, major |
|
|
| **Performance** | Response times (P50/P95/P99), CPU/memory, throughput |
|
|
| **Dependencies** | Total count, outdated, security vulnerabilities |
|
|
| **Build** | Build time, test execution time, deployment time |
|
|
|
|
## 6c. Compare Against Baseline
|
|
|
|
1. Read `RUN_DIR/baseline_metrics.md`
|
|
2. Produce a side-by-side comparison: baseline vs final for every metric
|
|
3. Flag any regressions (metrics that got worse)
|
|
4. Verify acceptance criteria are met
|
|
|
|
Write `RUN_DIR/verification_report.md`:
|
|
- Test results summary: total, passed, failed, skipped
|
|
- Metric comparison table: metric, baseline value, final value, delta, status (improved / unchanged / regressed)
|
|
- Acceptance criteria checklist: criterion, status (met / not met), evidence
|
|
- Regressions (if any): metric, severity, explanation
|
|
|
|
**Self-verification**:
|
|
- [ ] All tests pass (zero failures)
|
|
- [ ] All acceptance criteria are met
|
|
- [ ] No critical metric regressions
|
|
- [ ] Metrics are captured with the same tools/methodology as Phase 0
|
|
|
|
**Save action**: Write `RUN_DIR/verification_report.md`
|
|
|
|
**GATE (BLOCKING)**: All tests must pass and no critical regressions. Present verification report to user. Do NOT proceed to Phase 7 until user confirms.
|