Compare commits
1 Commits
6c9746eb05
...
c57f4b67ff
| Author | SHA1 | Date | |
|---|---|---|---|
|
c57f4b67ff
|
@@ -1,14 +0,0 @@
|
|||||||
---
|
|
||||||
name: Always include tests with changes
|
|
||||||
description: All code changes must include appropriate tests; never ship untested code
|
|
||||||
type: feedback
|
|
||||||
---
|
|
||||||
|
|
||||||
All changes (new features, bug fixes, refactors) must include tests as part of the same implementation. Do not ship code without accompanying tests.
|
|
||||||
|
|
||||||
**Why:** User explicitly called out that tests were missing from Issue #1 implementation and expects tests to always accompany changes going forward.
|
|
||||||
|
|
||||||
**How to apply:**
|
|
||||||
- Go backend: add `_test.go` files alongside changed packages, using `httptest` for handler tests and a real (or in-memory) DB for store tests
|
|
||||||
- Frontend: add `.test.tsx` files alongside new/changed pages and components using React Testing Library
|
|
||||||
- Tests go in the same PR/commit as the code they cover — never as a follow-up
|
|
||||||
@@ -6,10 +6,7 @@
|
|||||||
"Bash(go build ./...)",
|
"Bash(go build ./...)",
|
||||||
"Bash(go vet ./...)",
|
"Bash(go vet ./...)",
|
||||||
"Bash(go test -count=1 -v -coverprofile=coverage.out ./...)",
|
"Bash(go test -count=1 -v -coverprofile=coverage.out ./...)",
|
||||||
"Bash(go tool cover -func=coverage.out)",
|
"Bash(go tool cover -func=coverage.out)"
|
||||||
"Bash(tea issue:*)",
|
|
||||||
"Bash(go test:*)",
|
|
||||||
"Bash(npm test:*)"
|
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user