@boopkit/cap-testing 0.5.4 → 0.5.7

package/README.md

@@ -13,7 +13,7 @@ Agent skills plus a minimal Jest + ts-jest scaffold. The scaffold is intentional
 Copied into your project on install:
 
 - `jest.config.js` — ts-jest preset, Node test environment, test matcher at `tests/**/*.test.ts`, and the worker settings the suite runs under (`maxWorkers: 4`, `workerIdleMemoryLimit: '500MB'`). Those two spread test files across a pool of worker processes Jest recycles as they grow, so a long suite's memory stays bounded instead of climbing until it dies. They live in the config rather than in the `test` script so that focused runs — `npx jest tests/foo.test.ts` — inherit them too. Because files now run concurrently, tests must namespace whatever they create; drop `maxWorkers` to 1 if a suite is not isolation-safe yet.
-- `tsconfig.test.json` — extends your project tsconfig and includes `tests/`
+- `tsconfig.test.json` — extends your project tsconfig and includes `tests/`, widening `rootDir` to the project and naming its `@types` packages so that `src/` and `tests/` compile as one program on any TypeScript major. Its comments explain each setting.
 - `tests/app.test.ts` — a starter test asserting the Express app boots and has body parsing wired
 
 ### Scripts added to `package.json`
@@ -22,6 +22,9 @@ Copied into your project on install:
 |--------|---------|
 | `test` | `jest` |
 | `test:watch` | `jest --watch` |
+| `typecheck` | `tsc -p tsconfig.test.json` |
+
+`typecheck` is the whole-program static check the testing and planning skills tell every task to run alongside its focused tests: it sees every caller of what changed, which is the breakage a focused run is blind to.
 
 ### Skills installed
 
@@ -37,9 +40,12 @@ Copied into `skills/` on install:
 
 **npm devDependencies added to your project:**
 
-- `jest` — test runner
-- `ts-jest` — TypeScript preset for Jest
-- `@types/jest` — TypeScript types for Jest
+- `jest@^30` — test runner
+- `ts-jest@^29` — TypeScript preset for Jest
+- `@types/jest@^30` — TypeScript types for Jest
+- `typescript@^5` — required by `ts-jest` and by the `typecheck` script
+
+Each is pinned to a caret major so that the toolchain a new project receives is the one boop runs its own suite against, rather than whatever shipped most recently.
 
 **Environment variables:** none required for the scaffold. Individual tests may need service credentials (the Express testing skill documents the integration-test prerequisites — local Postgres, etc.) — those are project-specific and not enforced by this capability.
 

package/capability.json

@@ -4,9 +4,10 @@
   "type": "development",
   "dependencies": [],
   "devDependencies": [
-    "jest",
-    "ts-jest",
-    "@types/jest"
+    "jest@^30",
+    "ts-jest@^29",
+    "@types/jest@^30",
+    "typescript@^5"
   ],
   "files": [
     "jest.config.js",
@@ -26,6 +27,10 @@
     "test:watch": {
       "cmd": "jest --watch",
       "description": "Run tests in watch mode"
+    },
+    "typecheck": {
+      "cmd": "tsc -p tsconfig.test.json",
+      "description": "Type-check src/ and tests/ as one program"
     }
   },
   "skill_migrations": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cap-testing",
-  "version": "0.5.4",
+  "version": "0.5.7",
   "description": "Jest testing setup and testing skills for AI agents",
   "files": [
     "scaffold/",

package/scaffold/tsconfig.test.json

@@ -1,5 +1,26 @@
 {
+  // The config ts-jest type-checks against, and the one to point a static
+  // check at: `npx tsc -p tsconfig.test.json`.
   "extends": "./tsconfig.json",
+  "compilerOptions": {
+    // The base config sets "rootDir": "src" so a build emits dist/ cleanly.
+    // Tests live outside src/, so inheriting that root makes every one of them
+    // a TS6059 "not under rootDir" error before a single assertion is read.
+    // Widening the root to the project is what lets tests and sources share a
+    // program; nothing is emitted from here, so the narrower build root is
+    // unaffected.
+    "rootDir": ".",
+    // Type-check only. Without this a stray `tsc -p tsconfig.test.json` would
+    // emit compiled tests into dist/ alongside the real build output.
+    "noEmit": true,
+    // Name the type packages explicitly instead of relying on TypeScript
+    // pulling in everything under node_modules/@types. That automatic
+    // inclusion is not dependable across TypeScript majors — under 6.x it
+    // stops finding @types/jest here, and every `describe`/`it`/`expect` in
+    // the suite becomes TS2593/TS2304 while the package sits installed and
+    // correct. Listing them costs nothing and does not change on upgrade.
+    "types": ["jest", "node"]
+  },
   "include": ["src/**/*", "tests/**/*"],
   "exclude": ["node_modules", "dist"]
 }

package/skills/boop-testing-tdd-light/SKILL.md

@@ -4,6 +4,11 @@ description: "When you need to build features, implement changes, or fix bugs, f
 metadata:
   category: test
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Light TDD Flow
 
 Red → Green → Refactor. Document "before" and "after" states.

package/skills/boop-testing-testing/SKILL.md

@@ -4,6 +4,11 @@ description: "When you need to write, run, or reason about tests in this project
 metadata:
   category: test
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Testing
 
 
@@ -62,6 +67,10 @@ A skip carrying neither a ticket reference nor a `SKIP-OK:` reason is a conventi
 
 **The rule.** A change runs the focused tests for what it touched, plus the project's whole-program static check. The full suite runs once per branch, on the work that completes it. The `boop-project-mgmt-beads-planning` skill carries the canonical wording to put on issues; this section is the reasoning behind it, and the two have to keep agreeing.
 
+**The command is `npm run typecheck`** — `tsc -p tsconfig.test.json`, which compiles `src/` and `tests/` as one program and emits nothing. `boop add testing` scaffolds the script and the config together, so in any project with this capability the static check has a name rather than an invocation each agent has to derive.
+
+If a project does not have it, add it before following the rule, and check the config before trusting it. A `tsconfig.test.json` that extends a build config and then includes `tests/**/*` inherits `"rootDir": "src"`, and every test file is then a TS6059 "not under rootDir" before a single assertion is read — a static check that fails on every file teaches an agent to skip it. The scaffolded config sets `"rootDir": "."`, `"noEmit": true` and an explicit `"types"` list for exactly that reason; its comments explain each one.
+
 **Why the whole suite is the wrong tool mid-change.** The problem is localization, first and foremost. Break a shared dependency and the suite reports it as a cascade of failures in tests that never mention the thing you changed, and you are then reading a wall of red to reconstruct a fact the type-checker would have told you outright, naming a file and a line. A static check plus a search for callers answers "does everything that uses this still hold?" both faster and more precisely than the suite does.
 
 Second, it is slower than the focused run, though see the caution below about how much weight that carries.

package/skills/boop-testing-testing-express-web/SKILL.md

@@ -4,6 +4,11 @@ description: "When you need to write or run tests for the Express server — ser
 metadata:
   category: test
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Testing: Express App (Web & APIs)