Files
gps-denied-onboard/.claude/commands/plan/templates/resource-limit-tests.md
T
Yuzviak 6ff14a1a7d chore: import .claude command skills, CLAUDE.md, .gitignore, next_steps.md
- Vendor local .claude/ command skills (autopilot, plan, implement, etc.)
- Add CLAUDE.md pointing slash commands to .claude/commands/*/SKILL.md
- Untrack docs-Lokal/ and ignore .planning/ for local-only planning docs
- Include next_steps.md pulled from upstream

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-16 21:39: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.