You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c16e242
Browse filesBrowse the repository at this point in the historyBrowse files
Remove capability tests that duplicate existing package-manager routing coverage
getPackageManagerCapability resolves its manager via the same
PythonEnvironmentManagers.getPackageManager routing already used by
getPackages/managePackages/refreshPackages, and already exhaustively
tested in packageManager.api.unit.test.ts. Several tests in
extensionApi.capabilities.unit.test.ts re-exercised that same
pre-existing routing (project inference, ambiguous/missing project
fallback prevention) through the new capability entry point without
testing anything specific to capability advertisement:
- 'queries the preferred non-project package provider without project
inference' duplicated the project-independent manager tests.
- 'environment routing infers a unique project and selects its
different configured provider' duplicated the unique-project
resolution test.
- 'does not fall back to a project-aware root with 0/2 matching
projects' duplicated the ambiguous/missing project tests.
Simplified 'a missing configured provider cannot fall back to the
preferred root' to only cover the explicit-project path, which is
genuinely new (no other package method accepts an explicit project
override), dropping the environment-only variant that duplicated the
existing undefined-manager-id lookup behavior. Removed the now-unused
getLastKnownEnvironment stub that only the deleted tests relied on.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments