The Package pillar of the public API (managePackages, getPackages, refreshPackages) is backed by src/managers/builtin/pipPackageManager.ts and src/managers/conda/condaPackageManager.ts, and neither has a direct unit test. Only their helper utilities (pipListUtils, pipUtils, installArgs, normalizePackageName) and the host-based packageManagement.integration.test.ts provide coverage, so the manager classes' own logic (install/uninstall dispatch, change-event firing, error propagation) is untested at the unit level.
@edvilme you pick to decide exactly how this should look. I think unit test plus some sort of integration test would be ideal.
The
Packagepillar of the public API (managePackages,getPackages,refreshPackages) is backed bysrc/managers/builtin/pipPackageManager.tsandsrc/managers/conda/condaPackageManager.ts, and neither has a direct unit test. Only their helper utilities (pipListUtils,pipUtils,installArgs,normalizePackageName) and the host-basedpackageManagement.integration.test.tsprovide coverage, so the manager classes' own logic (install/uninstall dispatch, change-event firing, error propagation) is untested at the unit level.@edvilme you pick to decide exactly how this should look. I think unit test plus some sort of integration test would be ideal.