Scope: medium Risk: low Spec: misaligned Type: feature
Summary: Issue #170 title says 'TEST-003: Chaos Engineering Tests' but per MILESTONES.md #170 is DEV-003 (Developer onboarding guide), TEST-003 (#163) is Performance/load testing, and Chaos engineering is TEST-004 (#164) — the issue body is empty.
Suggestion: Resolve the title/assignment mismatch first — retitle or reassign to correct issue number. If chaos tests are the intent: (1) create tests/chaos/ directory with pytest scenarios for node crash, network partition, service outage, and resource exhaustion; (2) expand scripts/chaos_test.py beyond the single node_crash scenario; (3) the existing docs (CHAOS_TESTING.md, TESTING_GUIDE.md) already specify exact behavior expectations and should serve as the spec.
Rationale: SCOPE=medium: requires a new tests/chaos/ directory, 4+ scenario modules, and expansion of the existing chaos CLI (5-10 new files). RISK=low: purely additive test infrastructure — no changes to core runtime or substrate paths. SPEC=misaligned: the title+number contradicts MILESTONES.md's assignment table (#170=DEV-003, not TEST-003); the body is empty so intent is ambiguous. TYPE=feature: this adds a new testing capability (resilience/chaos testing) that doesn't currently exist as an automated test suite — only a skeleton CLI with one scenario exists.

To unblock: Remove the blocked:needs-decision label. The triage will apply the appropriate outcome based on your choice above.

## ⏸ Needs Decision **What needs to be decided?** - **Should the spec be adjusted or is this still worth doing?** If yes, remove the `blocked:needs-decision` label and the triage will approve it. **Blocking factors:** - **Spec misaligned** — doesn't align with project direction --- **Scope:** medium **Risk:** low **Spec:** misaligned **Type:** feature **Summary:** Issue #170 title says 'TEST-003: Chaos Engineering Tests' but per MILESTONES.md #170 is DEV-003 (Developer onboarding guide), TEST-003 (#163) is Performance/load testing, and Chaos engineering is TEST-004 (#164) — the issue body is empty. **Suggestion:** Resolve the title/assignment mismatch first — retitle or reassign to correct issue number. If chaos tests are the intent: (1) create `tests/chaos/` directory with pytest scenarios for node crash, network partition, service outage, and resource exhaustion; (2) expand `scripts/chaos_test.py` beyond the single `node_crash` scenario; (3) the existing docs (CHAOS_TESTING.md, TESTING_GUIDE.md) already specify exact behavior expectations and should serve as the spec. **Rationale:** SCOPE=medium: requires a new `tests/chaos/` directory, 4+ scenario modules, and expansion of the existing chaos CLI (5-10 new files). RISK=low: purely additive test infrastructure — no changes to core runtime or substrate paths. SPEC=misaligned: the title+number contradicts MILESTONES.md's assignment table (#170=DEV-003, not TEST-003); the body is empty so intent is ambiguous. TYPE=feature: this adds a new testing capability (resilience/chaos testing) that doesn't currently exist as an automated test suite — only a skeleton CLI with one scenario exists. **To unblock:** Remove the `blocked:needs-decision` label. The triage will apply the appropriate outcome based on your choice above.

Mark added the

blocked:preflight

label

2026-07-31 04:26:45 +00:00

Mark closed this issue

2026-08-11 03:53:43 +00:00

Mark commented

2026-08-11 03:53:43 +00:00

Author

Owner

TEST-003 Chaos Engineering Tests — spec misaligned, closing as wontfix

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Mark/mesh-seed#170

No description provided.

Rows
Columns