Add smoke test for installed source wired to real AppAgentHostApplicator
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- testing
Research direction
Start with createDefaultInstalledAgentSource, AppAgentHostApplicator, and the command-lock setup, then review the existing source lifecycle/barrier tests and appAgentHost.spec.ts. Add a thin smoke/integration test covering install, update, and uninstall through the real components. Done means replacement is verified to use one lock section without exposing both old and new providers.
Written by the indexing model from the issue text.
Description
Summary
Add a thin smoke/integration test that wires the installed-agent source lifecycle to the real AppAgentHostApplicator.
Background
The source lifecycle/barrier tests use faithful fake hosts, and the single-lock/no-interleave invariant is pinned in appAgentHost.spec.ts. What is missing is a small test that composes the real installed source path with the real dispatcher applicator, so a future regression from coordinated replaceProvider back to naive remove+add would fail outside the isolated unit test.
Suggested Coverage
- install/update/uninstall through
createDefaultInstalledAgentSource - a real
AppAgentHostApplicatorusing a real command lock - assertion that replacement runs under the intended single-lock section and does not expose old+new coexistence
Source
Deferred from PR #2611 review-log cleanup.
- Dominant language
- TypeScript
- Stars
- 744
- Forks
- 107
- Avg merge
- 1d 59m
- Merged PRs (30d)
- 113
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No 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 microsoft/TypeAgent
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Add CI validation for schema keyword driftMay be free again @GeorgeNgMsft claimed this 32 days ago, and no pull request is open. Open
microsoft/TypeAgent#2978 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
dispatcher enhancement security
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in microsoft/TypeAgent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Comfy-Org/ComfyUI_frontend#20346 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
decentralized-identity/didwebvh-ts#203 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lingdojo/kana-dojo#31791 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Telegram webhook: line breaks lost since switch to rich messagesPossibly taken @Kshot3000 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
github_actions security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day