test: cover registered package manager lifecycles

[Eduardo Villalpando Mello (edvilme)]

Summary

Adds a package-manager-centric integration baseline that intentionally precedes and de-risks #1686, so the package-manager command refactor is exercised against behavior established on main.

• drives one stateful install/list/direct-package/uninstall lifecycle per active profile
• uses unique disposable projects and manager-owned disposable environments
• exercises the live registered manager instances through a runtime-gated integration-test bridge
• guards registry completeness so every registered package-manager ID has an active fixture or explicit deferral
• covers normal Pip execution and Conda when their runtime prerequisites are available
• records an uncached baseline instead of assuming a newly created environment is empty
• restores workspace-scoped configuration from inspect() snapshots and performs guarded failure-safe cleanup
• defers Poetry pending a Poetry-owned project/lockfile lifecycle
• defers uv-backed Pip because changing the machine-scoped selection reliably within one extension host was not stable on main, while available-version lookup would also introduce uv tool run pip network seeding
• pins the disposable integration-test user profile to normal Pip execution

Validation

• npm run compile
• npm run compile-tests
• npm run lint
• npm run unittest
• targeted packageManagement.integration.test.js: 3 passing, 2 prerequisite skips locally
  • Pip skipped because quick create selected Python 3.15.0 alpha, whose bundled Pip metadata is incomplete
  • Conda skipped because Conda is not installed
• reviewer specialist: clean, no Critical or Important findings

The active Pip and Conda fixtures require package-index/network access when their runtime prerequisites are present.

Fixes #1701

[Copilot]

Pull request overview

Adds a package-manager-centric integration baseline to exercise install/list/direct-deps/uninstall lifecycles against the live registered package manager instances, establishing behavioral coverage ahead of the package-manager command refactor work.

Changes:

• Adds a fixture registry describing active/deferred package managers and their expected capabilities.
• Reworks the integration test to drive a disposable project + disposable environment lifecycle per active profile, with registry completeness guards and prerequisite-based skips.
• Adds an integration-test-only API bridge (env-gated) to expose the live registered PackageManager implementations, and pins the integration test user profile to normal pip execution (python-envs.alwaysUseUv=false).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/test/integration/packageManagerFixtures.ts	Introduces fixture definitions for registered package managers, capabilities, and per-manager profiles (active vs deferred).
src/test/integration/packageManagement.integration.test.ts	Implements the fixture-driven integration lifecycle tests and registry completeness checks, plus robust cleanup and prerequisite skips.
src/internal.api.ts	Adds a registeredManager getter on InternalPackageManager to expose the wrapped live implementation for tests.
src/extension.ts	Env-gated integration-test bridge that exposes registered package managers via the exported API object.
.vscode-test.mjs	Seeds integration test user settings to force python-envs.alwaysUseUv=false for consistent pip execution during integration runs.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/test/integration/packageManagement.integration.test.ts:150

• addPythonProject is a synchronous (void-returning) API, so await here is redundant and can confuse readers (and may be flagged by @typescript-eslint/await-thenable if enabled).

        await api.addPythonProject(project);

[Stella Huang (StellaHuang95)]

🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR.

[Eleanor Boyd (eleanorjboyd)]

Production/API findings 1–3 from my review. Tests were reviewed by inspection but not executed.

written by my agent

[Rich Chiodo (rchiodo)]

The new integration baseline can skip real environment creation and available-version failures, and it does not establish a pre-install package baseline. These gaps can mask regressions and invalidate the lifecycle assertions.

[Rich Chiodo (rchiodo)]

The new integration baseline can skip active-manager failures and does not establish the claimed lifecycle coverage before mutating environments. These gaps can hide regressions in environment creation and package-manager operations.

[Rich Chiodo (rchiodo)]

Approved via Review Center.

[Rich Chiodo (rchiodo)]

Warning · Non-blocking recommendation

When requests is already installed, both mutation calls are skipped and the lifecycle passes without testing install or uninstall. Select a package absent from the baseline, or skip/fail this fixture explicitly so a passing run always proves both transitions.

[Rich Chiodo (rchiodo)]

Warning · Non-blocking recommendation

Missing Pip metadata makes supportsVersionLookup return false, potentially converting a package-list parsing regression into a passing skip. Require the Pip package/version to be present, and skip only when its parsed version is concretely below 21.2.

[Rich Chiodo (rchiodo)]

Approved via Review Center.