bmad-method-test-architecture-enterprise 1.5.2 → 1.5.3

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.5.2",
+  "version": "1.5.3",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",

package/release_notes.md

@@ -1,13 +1,10 @@
-## 🚀 What's New in v1.5.2
-
-### ✨ New Features
-- feat: harden pact framework and knowledge
+## 🚀 What's New in v1.5.3
 
 ### 🐛 Bug Fixes
-- fix: pr comments
+- fix: tweak pactjs instructions
 
 ### 📦 Other Changes
-- Merge pull request #51 from bmad-code-org/feat/harden-pact-framework-flow
+- Merge pull request #52 from bmad-code-org/fix/tweak-pactjs-instructions
 
 
 ## 📦 Installation
@@ -17,4 +14,4 @@ npx bmad-method install
 # Select "Test Architect" from module menu
 ```
 
-**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.5.1...v1.5.2
+**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.5.2...v1.5.3

package/src/testarch/knowledge/contract-testing.md

@@ -130,7 +130,7 @@ describe('User API Contract', () => {
             'Content-Type': 'application/json',
             Accept: 'application/json',
           },
-          body: like(newUser),
+          body: newUser,
         })
         .willRespondWith({
           status: 201,
@@ -176,7 +176,7 @@ describe('User API Contract', () => {
 **Key Points**:
 
 - **Consumer-driven**: Frontend defines expectations, not backend
-- **Matchers**: `like`, `string`, `integer` for flexible matching
+- **Matchers (Postel's Law)**: Use `like`, `string`, `integer` matchers in `willRespondWith` (responses) for flexible matching. Do NOT use `like()` on request bodies in `withRequest` — the consumer controls what it sends, so request bodies should use exact values. This follows Postel's Law: be strict in what you send (requests), be lenient in what you accept (responses).
 - **Provider states**: given() sets up test preconditions
 - **Isolation**: No real backend needed, runs fast
 - **Pact generation**: Automatically creates JSON pact files

package/src/testarch/knowledge/pact-consumer-framework-setup.md

@@ -418,15 +418,15 @@ describe('Movies API Consumer Contract', () => {
       )
       .willRespondWith(
         200,
-        setJsonContent({
-          body: like({
+        setJsonBody(
+          like({
             id: integer(1),
             name: string('The Matrix'),
             year: integer(1999),
             rating: like(8.7),
             director: string('Wachowskis'),
           }),
-        }),
+        ),
       )
       .executeTest(async (mockServer: V3MockServer) => {
         // Inject mock server URL into the REAL consumer code
@@ -617,6 +617,8 @@ Before presenting the consumer CDC framework to the user, verify:
 - [ ] Consumer tests use `.pacttest.ts` extension
 - [ ] Consumer tests use PactV4 `addInteraction()` builder
 - [ ] Interaction callbacks use `setJsonContent` for query/header/body and `setJsonBody` for body-only responses
+- [ ] Request bodies use exact values (no `like()` wrapper) — Postel's Law: be strict in what you send
+- [ ] `like()`, `eachLike()`, `string()`, `integer()` matchers are only used in `willRespondWith` (responses), not in `withRequest` (requests)
 - [ ] Consumer tests call REAL consumer code (actual API client functions), NOT raw `fetch()`
 - [ ] Consumer code exposes URL injection mechanism (`setApiUrl()`, env var, or constructor param)
 - [ ] Local consumer-helpers shim present if pactjs-utils not installed

package/src/workflows/testarch/automate/steps-c/step-03a-subagent-api.md

@@ -97,6 +97,7 @@ test.describe('[Feature] API Tests', () => {
 - ✅ Generate request filter helpers in `pact/http/helpers/` using `createRequestFilter({ tokenGenerator: () => string })`
 - ✅ Generate shared state constants in `pact/http/helpers/states.ts`
 - ✅ If async/message patterns detected, generate message consumer tests in `pact/message/` using `buildMessageVerifierOptions`
+- ⚠️ **Postel's Law for matchers**: Use `like()`, `eachLike()`, `string()`, `integer()` matchers ONLY in `willRespondWith` (responses). Request bodies in `withRequest` MUST use exact values — never wrap request bodies in `like()`. The consumer controls what it sends, so contracts should be strict about request shape.
 
 ### 3. Track Fixture Needs