mirror of
https://github.com/azaion/admin.git
synced 2026-04-22 22:46:33 +00:00
Oleksandr Bezdieniezhnykh
36 lines
944 B
Markdown
36 lines
944 B
Markdown
# Performance Tests Template
|
|
|
|
Save as `DOCUMENT_DIR/tests/performance-tests.md`.
|
|
|
|
---
|
|
|
|
```markdown
|
|
# Performance Tests
|
|
|
|
### NFT-PERF-01: [Test Name]
|
|
|
|
**Summary**: [What performance characteristic this validates]
|
|
**Traces to**: AC-[ID]
|
|
**Metric**: [what is measured — latency, throughput, frame rate, etc.]
|
|
|
|
**Preconditions**:
|
|
- [System state, load profile, data volume]
|
|
|
|
**Steps**:
|
|
|
|
| Step | Consumer Action | Measurement |
|
|
|------|----------------|-------------|
|
|
| 1 | [action] | [what to measure and how] |
|
|
|
|
**Pass criteria**: [specific threshold — e.g., p95 latency < 400ms]
|
|
**Duration**: [how long the test runs]
|
|
```
|
|
|
|
---
|
|
|
|
## Guidance Notes
|
|
|
|
- Performance tests should run long enough to capture steady-state behavior, not just cold-start.
|
|
- Define clear pass/fail thresholds with specific metrics (p50, p95, p99 latency, throughput, etc.).
|
|
- Include warm-up preconditions to separate initialization cost from steady-state performance.
|