Add feed materialize harness for installed-source update/prune coverage
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- testing
Research direction
Start with createDefaultInstalledAgentSource and the existing coverage in installSourcesFeed.spec.ts and installSourcesInstalledProvider.spec.ts. Trace how the installed source reaches feed materialization, then add one shared test seam and cover feed-driven prune, rollback/commit mirror pruning, and package update re-resolution through the installed-source path.
Written by the indexing model from the issue text.
Description
Summary
Add a hermetic feed-materialize test harness for the installed-agent source so update/prune behavior can be exercised through the real source path instead of path-record stand-ins.
Background
During the install-source/update-coordination work, several coverage gaps were intentionally deferred because createDefaultInstalledAgentSource does not currently expose a feed dependency injection seam. Direct feed materialization is covered in installSourcesFeed.spec.ts, and update/prune behavior is covered through path-record stand-ins in installSourcesInstalledProvider.spec.ts, but the combined end-to-end feed-through-installed-source cases are not covered.
Coverage To Add
- feed-driven prune-on-swap and prune-after-uninstall through
createDefaultInstalledAgentSource - rollback prune of a real distinct v2 install root, plus the commit mirror where v2 is kept and v1 is pruned
- feed
@package update NAME RANGEre-resolution through the installed-source update path
Possible Approach
Add a feedDeps / npmInstall injection seam to createDefaultInstalledAgentSource, or expose a narrower test hook that lets the installed-source tests drive a mocked feed materialize. Prefer one seam that covers all three cases rather than separate production-only hooks.
Source
Deferred from PR #2611 review-log cleanup.
- Dominant language
- TypeScript
- Stars
- 749
- Forks
- 108
- 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 37 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