@boopkit/cap-testing 0.5.6 → 0.5.8

package/package.json

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

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,7 +67,7 @@ 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.
+**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. A focused run names its files: `npx jest <path>`, with one or more test files or folders. It reads the same `jest.config.js` as the full suite, so it runs under the same worker settings.
 
 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.
 
@@ -186,7 +191,7 @@ When a bug is discovered through manual testing or UAT, follow this checklist:
 
 1. **Reproduce** — confirm the failure and understand the root cause.
 2. **Find the test gap** — look for an existing test that *should* have caught it. If one exists, understand why it didn't (usually: it mocked the boundary where the failure lives).
-3. **Write a failing test first** — TDD applies to bug fixes, not just features. Write a test that reproduces the exact failure, confirm it fails for the right reason (Red), *then* apply the fix (Green). See [tdd-light.skill.md](test.tdd-light.skill.md).
+3. **Write a failing test first** — TDD applies to bug fixes, not just features. Write a test that reproduces the exact failure, confirm it fails for the right reason (Red), *then* apply the fix (Green). See [`boop-testing-tdd-light`](../boop-testing-tdd-light/SKILL.md).
 4. **Choose the right test level** — if the bug occurred at a system boundary (database, external API, serialization), the test must cross that boundary. A mock-based test cannot catch a boundary failure.
 
 ---
@@ -217,12 +222,11 @@ When code produces a schema or structure that is validated by an external system
 
 | Subsystem | Skill |
 |---|---|
-| Express app (web & APIs) | [testing-express-web.skill.md](testing-express-web.skill.md) — Jest, HTTP route tests, CLI tools, test helpers |
-| Cloudflare edge workers | [testing-cf-workers.skill.md](testing-cf-workers.skill.md) — Worker unit/integration tests, wrangler dev setup |
+| Express app (web & APIs) | [`boop-testing-testing-express-web`](../boop-testing-testing-express-web/SKILL.md) — Jest, HTTP route tests, CLI tools, test helpers |
 
 ---
 
 ## References
 
-- [development.skill.md](development.skill.md) — Light TDD Flow, completion criteria
+- `boop-coding-development` — Light TDD Flow, completion criteria
 - [jest.config.js](../../jest.config.js) — Jest configuration, at the project root this capability installs it to

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)