puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-07-29 12:01:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(task): add TDD pattern guidance to planner prompt

Browse Source 
When top-level task mentions "TDD" or "test-driven", planner now
creates test-first task pairs:
1. Write failing test (must fail for RIGHT reason, not syntax errors)
2. Make test pass (depends on failing test task)

This enforces TDD through task structure rather than acceptance criteria.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
This commit is contained in:
Mohamed Boudra
2026-01-15 10:09:39 +07:00
parent 02b3f83ae2
commit 5289be9c06
1 changed files with 34 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
packages/server/src/tasks/cli.ts
View File

@@ -585,12 +585,44 @@ Good examples:
- "File src/utils/parser.ts exports parseConfig function"
- "Running \`node cli.js --help\` prints usage information"
## TDD Pattern
When the top-level task mentions "TDD" or "test-driven", you MUST structure subtasks as test-first pairs:
1. **Write failing test** task (comes first)
- Acceptance criteria: test file exists AND test fails for the RIGHT reason
- The "right reason" means the test fails because the feature doesn't exist yet, NOT because of syntax errors, import errors, or unrelated failures
2. **Make test pass** task (depends on the failing test task)
- Acceptance criteria: the specific test passes AND overall test suite passes
Example breakdown for "Add user login endpoint (TDD)":
\`\`\`
task create "Write failing test for POST /api/login" --parent {parent_id} \\
--body "Write a test that calls POST /api/login with valid credentials and expects a JWT token response" \\
--accept "File src/auth/login.test.ts exists" \\
--accept "npm test fails with error message containing 'login' or 'api/login'" \\
--accept "Test failure is due to missing endpoint (404 or 'not found'), NOT syntax/import errors"
task create "Implement login endpoint to pass test" --parent {parent_id} --deps {previous_task_id} \\
--body "Implement POST /api/login to make the test pass" \\
--accept "npm test -- src/auth/login.test.ts passes" \\
--accept "POST /api/login with valid credentials returns 200 with JWT token"
\`\`\`
Key points:
- The failing test task MUST verify the test fails for the correct reason (missing feature, not broken code)
- The implementation task depends on the test task (enforced ordering)
- Each pair focuses on ONE specific behavior
## Your Options
1. If the current task is simple enough to implement directly, add a note explaining why and exit
2. If it needs breakdown, create subtasks with clear, verifiable acceptance criteria
3. If other tasks in the tree need reorganization based on what's been learned, do that
4. If a task is catastrophically stuck with no clear path forward (repeated failures WITHOUT progress), mark it failed
3. If TDD is requested, use the test-first pair pattern above
4. If other tasks in the tree need reorganization based on what's been learned, do that
5. If a task is catastrophically stuck with no clear path forward (repeated failures WITHOUT progress), mark it failed
Note: Multiple iterations are fine if there's progress. Only mark failed if truly stuck with no way forward.