@tekyzinc/gsd-t 2.1.0 → 2.2.0

package/commands/gsd-t-execute.md

@@ -27,10 +27,12 @@ For each task:
 3. Read the domain's constraints.md — follow all patterns
 4. Implement the task
 5. Verify acceptance criteria are met
-6. Run the Pre-Commit Gate checklist from CLAUDE.md — update ALL affected docs BEFORE committing
-7. Commit with a descriptive message: `[{domain}] Task {N}: {description}`
-8. Update `.gsd-t/progress.md` — mark task complete
-9. If you've reached a CHECKPOINT in integration-points.md, pause and verify the contract before continuing
+6. Run affected unit tests — fix any failures before proceeding
+7. If E2E framework exists and task changed UI/routes/flows: run affected E2E specs, update specs if needed
+8. Run the Pre-Commit Gate checklist from CLAUDE.md — update ALL affected docs BEFORE committing
+9. Commit with a descriptive message: `[{domain}] Task {N}: {description}`
+10. Update `.gsd-t/progress.md` — mark task complete
+11. If you've reached a CHECKPOINT in integration-points.md, pause and verify the contract before continuing
 
 ### Team Mode (when agent teams are enabled)
 Spawn teammates for independent domains:

package/commands/gsd-t-test-sync.md

@@ -15,9 +15,11 @@ Read:
 4. `.gsd-t/domains/{current}/tasks.md` — recent completed tasks
 
 Identify:
-- Test framework (pytest, jest, vitest, etc.)
+- **Unit/integration test framework** (pytest, jest, vitest, etc.)
+- **E2E test framework** (Playwright, Cypress, Puppeteer, etc.) — check for `playwright.config.*`, `cypress.config.*`, `playwright/`, `cypress/`, `e2e/`, or E2E-related dependencies in package.json/requirements.txt
 - Test directory structure
 - Naming conventions
+- Test run commands (from package.json scripts, Makefile, or CI config)
 
 ## Step 2: Map Code to Tests
 
@@ -77,6 +79,7 @@ Tests that sometimes fail:
 
 ## Step 4: Run Affected Tests
 
+### A) Unit/Integration Tests
 Execute tests that cover changed code:
 
 ```bash
@@ -87,7 +90,34 @@ pytest tests/test_{module}.py -v
 npm test -- --testPathPattern="{module}"
 ```
 
-Capture results:
+### B) E2E Tests
+If an E2E framework is detected, run E2E tests affected by the changes:
+
+```bash
+# Playwright
+npx playwright test {affected-spec}.spec.ts
+
+# Cypress
+npx cypress run --spec "cypress/e2e/{affected-spec}.cy.ts"
+```
+
+Determine which E2E specs are affected:
+- Changed a UI component or page? → Run specs that test that page/flow
+- Changed an API endpoint? → Run specs that exercise that endpoint
+- Changed auth/session logic? → Run all auth-related E2E specs
+- Changed database schema? → Run specs that depend on that data
+- Not sure what's affected? → Run the full E2E suite
+
+### C) Update E2E Tests
+If code changes affect user flows, update E2E test specs:
+- New pages/routes → create new E2E specs
+- Changed UI elements (selectors, text, layout) → update locators and assertions
+- Changed form fields or validation → update form fill steps and error assertions
+- New features → add E2E specs covering the happy path + key error cases
+- Removed features → remove or update affected E2E specs
+
+### D) Capture Results
+For all test types:
 - PASS: Test still valid
 - FAIL: Test needs update or code has bug
 - ERROR: Test broken (import error, etc.)
@@ -101,11 +131,13 @@ Create/update `.gsd-t/test-coverage.md`:
 
 ## Summary
 - Source files analyzed: {N}
-- Test files found: {N}
+- Unit/integration test files: {N}
+- E2E test specs: {N}
 - Coverage gaps: {N}
 - Stale tests: {N}
 - Dead tests: {N}
-- Tests passing: {N}/{total}
+- Unit tests passing: {N}/{total}
+- E2E tests passing: {N}/{total}
 
 ## Coverage Status
 
@@ -205,17 +237,20 @@ If issues found, add to current domain's tasks:
 ### During Execute Phase (auto-invoked):
 After each task completes:
 1. Quick scan of changed files
-2. Run affected tests
-3. If failures: pause and report
-4. If gaps: note for end-of-phase sync
-5. Continue execution
+2. Run affected unit/integration tests
+3. Run affected E2E tests (if E2E framework detected)
+4. If failures: pause and report
+5. If E2E specs need updating: update them before continuing
+6. If gaps: note for end-of-phase sync
+7. Continue execution
 
 ### During Verify Phase (auto-invoked):
 Full sync:
-1. Complete coverage analysis
-2. Run all tests
-3. Generate full report
-4. Block verification if critical tests failing
+1. Complete coverage analysis (unit + E2E)
+2. Run ALL unit/integration tests
+3. Run the FULL E2E test suite — this is mandatory, not optional
+4. Generate full report
+5. Block verification if any critical tests failing (unit or E2E)
 
 ### Standalone Mode:
 ```
@@ -238,19 +273,27 @@ Full sync:
 ```
 🧪 Test Sync Complete
 
-Results:
+Unit/Integration:
 - Tests run: 45
 - Passing: 43
 - Failing: 2
-- Coverage gaps: 3
+
+E2E ({framework}):
+- Specs run: 12
+- Passing: 11
+- Failing: 1
+
+Coverage:
+- Gaps: 3
 - Stale tests: 1
 - Dead tests: 0
 
 Action Required:
-- 2 failing tests must be fixed before verify passes
+- 2 failing unit tests must be fixed before verify passes
+- 1 failing E2E spec must be fixed before verify passes
 - See .gsd-t/test-coverage.md for details
 
-Generated 4 test tasks → added to current domain
+Generated 5 test tasks → added to current domain
 ```
 
 $ARGUMENTS

package/commands/gsd-t-verify.md

@@ -20,8 +20,9 @@ Standard dimensions (adjust based on project):
 2. **Contract Compliance**: Does every domain honor its contracts?
 3. **Code Quality**: Conventions, patterns, error handling, readability
 4. **Test Coverage**: Are critical paths tested? Are edge cases covered?
-5. **Security**: Auth flows, input validation, data exposure, dependencies
-6. **Integration Integrity**: Do the seams between domains hold under stress?
+5. **E2E Tests**: Run the full E2E suite (Playwright, Cypress, etc.) — all specs must pass
+6. **Security**: Auth flows, input validation, data exposure, dependencies
+7. **Integration Integrity**: Do the seams between domains hold under stress?
 
 ## Step 3: Execute Verification
 
@@ -32,6 +33,13 @@ Work through each dimension sequentially. For each:
 3. Record findings as PASS / WARN / FAIL with specifics
 4. If FAIL, create a remediation task
 
+**Mandatory test execution:**
+1. Run ALL unit/integration tests — every test must pass
+2. Detect E2E framework (check for `playwright.config.*`, `cypress.config.*`, E2E deps in package.json)
+3. If E2E framework exists, run the FULL E2E suite — every spec must pass
+4. If E2E specs are missing or stale, invoke `gsd-t-test-sync` to update them first, then re-run
+5. Tests are NOT optional — verification cannot pass without running them
+
 ### Team Mode (when agent teams are enabled)
 ```
 Create an agent team for verification:
@@ -88,6 +96,8 @@ Create or update `.gsd-t/verify-report.md`:
 - Functional: {PASS/WARN/FAIL} — {X}/{Y} criteria met
 - Contracts: {PASS/WARN/FAIL} — {X}/{Y} contracts compliant
 - Code Quality: {PASS/WARN/FAIL} — {N} issues found
+- Unit Tests: {PASS/WARN/FAIL} — {N}/{total} passing
+- E2E Tests: {PASS/WARN/FAIL} — {N}/{total} specs passing
 - Security: {PASS/WARN/FAIL} — {N} findings
 - Integration: {PASS/WARN/FAIL}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 27 slash commands with impact analysis, test sync, and milestone archival",
   "author": "Tekyz, Inc.",
   "license": "MIT",

package/templates/CLAUDE-global.md

@@ -133,8 +133,12 @@ BEFORE EVERY COMMIT:
   │     YES → Update .gsd-t/techdebt.md
   ├── Did I establish a pattern future work should follow?
   │     YES → Update CLAUDE.md or domain constraints.md
-  └── Did I add/change tests?
-        YES → Verify test names and paths are referenced in requirements
+  ├── Did I add/change tests?
+  │     YES → Verify test names and paths are referenced in requirements
+  ├── Did I change UI, routes, or user flows?
+  │     YES → Update affected E2E test specs (Playwright/Cypress)
+  └── Did I run the affected tests?
+        YES → Verify they pass. NO → Run them now.
 ```
 
 If ANY answer is YES and the doc is NOT updated, update it BEFORE committing. No exceptions.