Skip to content

refactor(create-expert): document why exec is used in expert-tester #374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FL4TLiN3 merged 1 commit into from
Jan 3, 2026
Merged

refactor(create-expert): document why exec is used in expert-tester #374

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .changeset/document-exec-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
"create-expert": patch
---

Document why exec is used in expert-tester

Added explanation that exec is used instead of delegation because:
- Tests need to run Experts as black-box (same as end-users)
- CLI execution ensures realistic test conditions
4 changes: 4 additions & 0 deletions apps/create-expert/src/lib/create-expert-toml.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,6 +375,10 @@ From the stage manager:
## Testing Process

### 1. Execute Tests

NOTE: We use \`exec\` instead of delegation because we need to test the Expert as a black-box,
exactly as end-users would run it via the CLI. This ensures realistic test conditions.

For each test case, run:
\`\`\`bash
npx -y perstack run expert-name "test query" --workspace . --filter completeRun
Expand Down