stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

test fixes and new product advisories work

Browse Source
This commit is contained in:
master
2026-01-28 02:30:48 +02:00
parent 82caceba56
commit 644887997c
288 changed files with 69101 additions and 375 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/code-of-conduct/CODE_OF_CONDUCT.md
View File

@@ -475,6 +475,19 @@ Test categorization:
* Use `[Trait("Category", "Unit")]` for unit tests.
* Use `[Trait("Category", "Integration")]` for integration tests.
### 9.1 Turn #6 testing enhancements
The following practices from TESTING_PRACTICES.md are required for compliance-critical and safety-critical modules:
* **Intent tagging**: Use `[Trait("Intent", "<category>")]` to classify test purpose (Regulatory, Safety, Performance, Competitive, Operational).
* **Observability contracts**: Validate OTel traces, structured logs, and metrics as APIs with schema enforcement.
* **Evidence traceability**: Link requirements to tests to artifacts for audit chains using `[Requirement("...", SprintTaskId = "...")]`.
* **Cross-version testing**: Validate N-1 and N+1 compatibility for release gating.
* **Time-extended testing**: Run longevity tests for memory leaks, counter drift, and resource exhaustion.
* **Post-incident replay**: Every P1/P2 incident produces a permanent regression test tagged with `[Trait("Category", "PostIncident")]`.
See [TESTING_PRACTICES.md](./TESTING_PRACTICES.md) for full details, examples, and enforcement guidance.
---
## 10. Documentation and sprint discipline