nexus-testinglisted

# Nexus Flaky Test Root Cause Analyzer Structured protocol for diagnosing, isolating, and permanently eliminating non-deterministic test failures. Not a retry wrapper — treats flakiness as a first-class defect. ``` name: nexus-testing category: testing / quality required_context: test file path, failure frequency, CI log or local output, stack trace if available expected_inputs: test name, framework, failure pattern, environment (local/CI/both), reproduction rate expected_outputs: flakiness type, reproduction steps, root cause (one sentence), narrowest fix + verification command, prevention recommendation ``` ## Core Principles 1. A test failing 1-in-20 runs is still failing — it is a false alarm factory. 2. A retry without investigation ships unknown risk. 3. Fix the root cause, not the symptom — masking a race condition makes it fail more often. 4. Never mark `xfail`/`skip` without a linked issue and expiry date. 5. Test flakiness often mirrors a real production concurrency or data integrity hazard. --- ## Step 1 — Collect Context Required before any investigation: | Signal | How | |--------|-----| | Failure rate | Estimate from CI history (1/5? 1/100?) | | Stack trace | Full verbatim trace from a failing run | | Test path | Exact: `tests/users/test_create.py::test_create_user` | | Framework + version | `pytest --version`, `jest --version`, `go version` | | CI vs local | Fails only in CI, only locally, or both? | | Parallelism