Fix stale test references in the task-execution and runtime READMEs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read packages/junior/src/chat/task-execution/README.md and packages/junior/src/chat/runtime/README.md, then inspect durable-queue.test.ts and the current integration test locations. Update or remove the stale outcome bullets and runtime coverage path, checking #2001 because its test move may change the references. Done means both READMEs point only to existing, relevant tests or omit the outdated references.
Written by the indexing model from the issue text.
Description
Two READMEs point to tests that no longer exist.
packages/junior/src/chat/task-execution/README.md
The section about durable-queue.test.ts lists the outcomes that the file covers. Two of them are not in the file:
- "Transient agent failure: failure before input commit retries without a Slack post; the retry limit stops with at most one fallback."
- "Mid-turn steer: a second
@mention folds into the active turn and still produces one final reply."
3a5be6f12 (#1571) removed both cases. durable-queue.test.ts now has six cases, and none of them covers these outcomes. #1398 still lists both as outcomes that durable-queue should own.
packages/junior/src/chat/runtime/README.md
Line 57 says: "Integration coverage lives under packages/junior/tests/integration/runtime/." That directory does not exist.
Change
- Point each bullet to the test that covers the outcome now, or remove the bullet.
- Fix or remove the runtime coverage path.
#2001 moves the tests that run the agent into packages/junior-evals. Check these references again when that work moves the tests.
Found in the test audit for #2001.
- Dominant language
- TypeScript
- Stars
- 367
- Forks
- 41
- Avg merge
- 6h 55m
- Merged PRs (30d)
- 164
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/junior
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
getsentry/junior#335 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
getsentry/junior#2100 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/junior
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
apache/rocketmq-dashboard#6610 ·
Maintainers usually reply within 3 days
-
nextjs-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
cloudflare/vinext#3920 ·
Maintainers usually reply within 1 day
-
Team:Dashboards
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
elastic/kibana#297299 · 1 comment ·
Maintainers usually reply within 1 day
-
analytics beginner friendly community contributions-welcome good first issue hacktoberfest help wanted up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days