Cistern Test Runner
Detect the Stack
Check for these files in the repo root:
go.mod→ Gopackage.json→ Node/TypeScriptpytest.ini,setup.py,pyproject.tomlwith pytest → PythonMakefilewith test target → Make
Build Commands
| Stack | Build |
|---|---|
| Go | go build ./... |
| Node/TS | npm run build or tsc --noEmit |
| Python | (no compile step) |
| Make | make build |
Test Commands
| Stack | Test |
|---|---|
| Go | go test ./... |
| Node/TS | npm test |
| Python | pytest |
| Make | make test |
Lint Commands
| Stack | Lint |
|---|---|
| Go | go vet ./... |
| Node/TS | npm run lint |
| Python | ruff check . |
| Make | make lint |
Rules
- Always run build before tests
- Run the full test suite (no
-runfiltering) unless diagnosing a specific failure - Signal pass only after all tests pass — zero failures, zero exceptions
- Failing tests = automatic recirculate (for review/QA cataractae) or must-fix (for implementer). This is unconditional — "pre-existing" failures are still failures. A red test suite means the codebase is broken. Fix it or recirculate; never pass with failing tests.