Pull request overview

Adds project-based support for unittest execution/discovery by using the Python Environments “project” model, ensuring the correct interpreter is used per project and that debug sessions are launched with project context.

Changes:

• Pass project.pythonProject into debug launch options for unittest (enables project-derived Python path/session naming).
• Prefer project.pythonEnvironment over getEnvironment(uri) when running discovery/execution via the env extension (pytest + unittest).
• Enable project-based execution in the test controller whenever projects exist (not only when pytest is enabled), plus add a targeted unittest execution unit test.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

src/client/testing/testController/controller.ts:805

• Project-based execution path bypasses the per-provider enablement checks. With this change, if hasProjects() is true, tests will be executed even when settings.testing.pytestEnabled/unittestEnabled are false (e.g. user disables a framework after discovery, but items still exist). Consider gating project execution on the relevant enabled setting(s) and/or filtering projects by project.testProvider against the current settings before calling executeTestsForProjects; otherwise fall back to unconfiguredWorkspaces behavior.

        // Check if we're in project-based mode and should use project-specific execution
        if (this.projectRegistry.hasProjects(workspace.uri)) {
            const projects = this.projectRegistry.getProjectsArray(workspace.uri);
            await executeTestsForProjects(projects, testItems, runInstance, request, token, {
                projectRegistry: this.projectRegistry,
                pythonExecFactory: this.pythonExecFactory,
                debugLauncher: this.debugLauncher,
            });
            return;
        }

src/client/testing/testController/unittest/testDiscoveryAdapter.ts:104

• The new project-aware environment selection (project?.pythonEnvironment ?? getEnvironment(uri)) in the env-extension execution path is not covered by unit tests for unittest discovery. Add a test that passes a ProjectAdapter with a known pythonEnvironment and asserts runInBackground is invoked with that environment (and that getEnvironment(uri) is not used).

            // Execute using environment extension if available
            if (useEnvExtension()) {
                traceInfo(`Using environment extension for unittest discovery in workspace ${uri.fsPath}`);
                const pythonEnv = project?.pythonEnvironment ?? (await getEnvironment(uri));
                if (!pythonEnv) {
                    traceError(
                        `Python environment not found for workspace ${uri.fsPath}. Cannot proceed with test discovery.`,
                    );
                    deferredTillExecClose.resolve();
                    return;
                }

src/client/testing/testController/pytest/pytestDiscoveryAdapter.ts:119

• The new project-aware environment selection (project?.pythonEnvironment ?? getEnvironment(uri)) in the env-extension execution path is not covered by unit tests for pytest discovery. Add a test that passes a ProjectAdapter with a known pythonEnvironment and asserts runInBackground is invoked with that environment (and that getEnvironment(uri) is not used).

            // Execute using environment extension if available
            if (useEnvExtension()) {
                traceInfo(`Using environment extension for pytest discovery in workspace ${uri.fsPath}`);
                const pythonEnv = project?.pythonEnvironment ?? (await getEnvironment(uri));
                if (!pythonEnv) {
                    traceError(
                        `Python environment not found for workspace ${uri.fsPath}. Cannot proceed with test discovery.`,
                    );
                    deferredTillExecClose.resolve();
                    return;
                }