You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/skills/testing.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,16 @@ Run this workflow before executing any test command:
71
71
- Do not report completion without runtime verification for the resolved target (unless blocked).
72
72
- Always report: should-run target, whether it was run, exact command, and pass/fail summary (or blocker).
73
73
74
+
## Test Configuration Hygiene (Mandatory)
75
+
76
+
- Do not add new environment variables to `tools/scenescape-start` for test-only behavior.
77
+
- Treat `tools/scenescape-start` as a stable shared launcher, not a per-test configuration surface.
78
+
- For test scenario inputs, prefer one of these paths:
79
+
- test configuration files (for example scenario JSON, service config JSON)
80
+
- test runner arguments (for example pytest options)
81
+
- Makefile variables scoped to test targets
82
+
- If a new environment variable is absolutely required for non-test runtime behavior, document and justify it in the related service docs; do not introduce it solely to satisfy a test matrix.
0 commit comments