test: remove skipped API key validation test from CLI integration tests

Author: AlePouroullis

tests/custom/integration/cli.test.ts

@@ -15,26 +15,26 @@ jest.setTimeout(40 * 1000); // 40 seconds
 
 /**
  * Runs the Humanloop CLI as a child process, executing the TypeScript source directly.
- * 
+ *
  * This function is used in integration tests to verify CLI behavior. Instead of using
  * the compiled JavaScript file (dist/cli.js), it runs the TypeScript source (src/cli.ts)
  * directly using ts-node. This approach:
- * 
+ *
  * 1. Eliminates the need for a build step before running tests
  * 2. Ensures tests always run against the latest source code
  * 3. Maintains process isolation for proper CLI testing
- * 
+ *
  * Implementation details:
  * - Uses child_process.spawn to run the CLI in a separate process
  * - Uses npx to execute ts-node without requiring it as a dependency
  * - Captures stdout/stderr for assertion in tests
  * - Returns a promise that resolves with the command output and exit code
- * 
+ *
  * Environment setup:
  * - Modifies PATH to prioritize the project's node_modules/.bin
  * - This ensures we use the project's TypeScript version
  * - Preserves all other environment variables
- * 
+ *
  * Example usage:
  * ```typescript
  * const result = await runCli([
@@ -46,7 +46,7 @@ jest.setTimeout(40 * 1000); // 40 seconds
  * expect(result.exitCode).toBe(0);
  * expect(result.stdout).toContain("Pull completed");
  * ```
- * 
+ *
  * @param args - Array of command line arguments to pass to the CLI
  * @returns Promise resolving to an object containing:
  *   - stdout: Standard output of the command
@@ -114,54 +114,6 @@ describe("CLI Integration Tests", () => {
         );
     });
 
-    /**
-     * NOTE: This test is currently skipped due to issues with CLI environment isolation.
-     *
-     * The test attempts to verify behavior when no API key is available, but faces
-     * challenges with how Node.js handles process execution during tests:
-     *
-     * 1. When executed via child_process.exec, the path to nonexistent env files
-     *    causes Node to return exit code 9 (SIGKILL) instead of the expected code 1
-     * 2. Shell interpretation of arguments makes it difficult to reliably test this edge case
-     *
-     * If this functionality needs testing, consider:
-     * - Using child_process.spawn for better argument handling
-     * - Unit testing the API key validation logic directly
-     * - Moving this test to a separate process with full environment isolation
-     *
-     * @see https://nodejs.org/api/child_process.html for more info on process execution
-     */
-    test.skip("pull_without_api_key: should show error when no API key is available", async () => {
-        // GIVEN a temporary directory and no API key
-        const { tempDir, cleanup } = createTempDir("cli-no-api-key");
-
-        // Create a path to a file that definitely doesn't exist
-        const nonExistentEnvFile = path.join(tempDir, "__DOES_NOT_EXIST__.env");
-
-        // WHEN running pull command without API key
-        const originalApiKey = process.env.HUMANLOOP_API_KEY;
-        delete process.env.HUMANLOOP_API_KEY;
-
-        const result = await runCli([
-            "pull",
-            "--local-files-directory",
-            tempDir,
-            "--env-file",
-            `"${nonExistentEnvFile}"`,
-        ]);
-
-        // Restore API key
-        process.env.HUMANLOOP_API_KEY = originalApiKey;
-
-        // THEN it should fail with appropriate error message
-        expect(result.exitCode).not.toBe(0);
-        expect(result.stderr + result.stdout).toContain(
-            "Failed to load environment file",
-        );
-
-        cleanup();
-    });
-
     test("pull_basic: should pull all files successfully", async () => {
         // GIVEN a base directory for pulled files
         const { tempDir, cleanup } = createTempDir("cli-basic-pull");