Files
gps-denied-onboard/.cursor/skills/plan/templates/resource-limit-tests.md
T
Oleksandr Bezdieniezhnykh 1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
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

809 B

Resource Limit Tests Template

Save as DOCUMENT_DIR/tests/resource-limit-tests.md.


# Resource Limit Tests

### NFT-RES-LIM-01: [Test Name]

**Summary**: [What resource constraint this validates]
**Traces to**: AC-[ID], RESTRICT-[ID]

**Preconditions**:
- [System running under specified constraints]

**Monitoring**:
- [What resources to monitor — memory, CPU, GPU, disk, temperature]

**Duration**: [how long to run]
**Pass criteria**: [resource stays within limit — e.g., memory < 8GB throughout]

Guidance Notes

  • Resource limit tests must specify monitoring duration — short bursts don't prove sustained compliance.
  • Define specific numeric limits that can be programmatically checked.
  • Include both the monitoring method and the threshold in the pass criteria.