tdd-enforcer 0.3.1 → 0.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -42,7 +42,7 @@ It locks files per phase — only test files in RED, only implementation files i
|
|
|
42
42
|
- `blockedInRed` — globs the agent **cannot** modify in RED phase (implementation files)
|
|
43
43
|
- `blockedInGreen` — globs the agent **cannot** modify in GREEN phase (test files)
|
|
44
44
|
- `!` exclusion prefix — optional, carves out subsets from a block list at init time. E.g. `!src/**/*.test.ts` excludes co-located test files from `blockedInRed` so the agent can write them in RED phase
|
|
45
|
-
- `testCommands` — shell commands to run tests
|
|
45
|
+
- `testCommands` — shell commands to run tests. **Runs sequentially** — each entry is started one after another. Use `&&` inside a single string entry to chain multiple commands in one step (e.g. `"npm run build && npm test"`). Do not rely on array ordering for dependency chains; put dependent commands in the same string entry with `&&`.
|
|
46
46
|
- `timeoutSeconds` — test timeout per command
|
|
47
47
|
|
|
48
48
|
2. **User** runs `/tdd:on` to enable enforcement.
|