idk

Author: eleanorjboyd

src/test/e2e/environmentDiscovery.e2e.test.ts

@@ -26,7 +26,6 @@
 import * as assert from 'assert';
 import * as vscode from 'vscode';
 import { ENVS_EXTENSION_ID } from '../constants';
-import { initializeTestSettings } from '../initialize';
 import { waitForCondition } from '../testUtils';
 
 suite('E2E: Environment Discovery', function () {
@@ -40,10 +39,6 @@ suite('E2E: Environment Discovery', function () {
     };
 
     suiteSetup(async function () {
-        // CRITICAL: Configure settings BEFORE extension activation
-        // This follows the vscode-python pattern of programmatic configuration
-        await initializeTestSettings();
-
         // Get and activate the extension
         const extension = vscode.extensions.getExtension(ENVS_EXTENSION_ID);
         assert.ok(extension, `Extension ${ENVS_EXTENSION_ID} not found`);

src/test/initialize.ts

@@ -23,7 +23,6 @@
 import * as assert from 'assert';
 import * as vscode from 'vscode';
 import { ENVS_EXTENSION_ID } from '../constants';
-import { initializeTestSettings } from '../initialize';
 import { TestEventHandler, waitForCondition } from '../testUtils';
 
 suite('Integration: Environment Manager + API', function () {
@@ -41,10 +40,6 @@ suite('Integration: Environment Manager + API', function () {
         // Set a shorter timeout for setup specifically
         this.timeout(20_000);
 
-        // CRITICAL: Configure settings BEFORE extension activation
-        // This follows the vscode-python pattern of programmatic configuration
-        await initializeTestSettings();
-
         const extension = vscode.extensions.getExtension(ENVS_EXTENSION_ID);
         assert.ok(extension, `Extension ${ENVS_EXTENSION_ID} not found`);
 

src/test/integration/envManagerApi.integration.test.ts

@@ -28,30 +28,21 @@
  * - Retries once on failure (configured in the runner)
  * - Tests are independent - no shared state between tests
  *
- * CRITICAL PATTERN (from vscode-python):
- * Settings must be configured PROGRAMMATICALLY before extension activation.
- * Relying solely on settings.json files can fail because:
- * - The ms-python.python extension may set useEnvironmentsExtension=false by default
- * - Settings files may not be loaded before activation
- * - Race conditions between file I/O and extension initialization
+ * NOTE: We do NOT install ms-python.python in test configuration.
+ * This is intentional - that extension defines python.useEnvironmentsExtension=false
+ * by default, which would cause our extension to skip activation.
+ * Without it installed, our extension uses its own default of true.
  */
 
 import * as assert from 'assert';
 import * as vscode from 'vscode';
 import { ENVS_EXTENSION_ID, MAX_EXTENSION_ACTIVATION_TIME } from '../constants';
-import { initializeTestSettings } from '../initialize';
 import { waitForCondition } from '../testUtils';
 
 suite('Smoke: Extension Activation', function () {
     // Smoke tests need longer timeouts - VS Code startup can be slow
     this.timeout(MAX_EXTENSION_ACTIVATION_TIME);
 
-    // CRITICAL: Configure settings BEFORE any test runs
-    // This follows the vscode-python pattern of programmatic configuration
-    suiteSetup(async function () {
-        await initializeTestSettings();
-    });
-
     /**
      * Test: Extension is installed and VS Code can find it
      *