@skyramp/mcp 0.0.17 → 0.0.19

package/build/index.js

@@ -16,7 +16,6 @@ import { registerIntegrationTestTool } from "./tools/generateIntegrationRestTool
 import { registerE2ETestTool } from "./tools/generateE2ERestTool.js";
 import { registerLoginTool } from "./tools/loginTool.js";
 import { registerLogoutTool } from "./tools/logoutTool.js";
-import { registerModularizationInstructions } from "./resources/modulazrizationInstructions.js";
 import { registerFixErrorTool } from "./tools/fixErrorTool.js";
 import { registerModularizationTool } from "./tools/modularizationTool.js";
 const server = new McpServer({
@@ -35,8 +34,6 @@ logger.info("Starting prompt registration process");
 registerTestGenerationPrompt(server);
 registerStartTraceCollectionPrompt(server);
 logger.info("All prompts registered successfully");
-// Register resources
-registerModularizationInstructions(server);
 // Register test generation tools
 registerSmokeTestTool(server);
 registerFuzzTestTool(server);

package/build/prompts/modularization-prompts.js

@@ -0,0 +1,100 @@
+export function getModularizationPrompt(filePath, language) {
+    return `
+**CRITICAL: Refactor code with modularization principles. Respond with complete, modularized code only WITHOUT ERRORS AND WRITTEN BACK TO THE FILE ${filePath}**
+
+**STEP 1: SEARCH & ANALYZE EXISTING CODE BASED ON TEST LANGUAGE AND NOT ALL LANGUAGE FILES - MANDATORY**
+You MUST search for existing test files by language and NOT ALL LANGUAGE FILES:
+${language === "python" ? `Python: .py files with "skyramp"` : ""}
+
+${language === "typescript" || language === "javascript"
+        ? `TypeScript/JavaScript: .ts/.js files with "@skyramp/skyramp"`
+        : ""}
+
+${language === "java" ? `Java: .java files with "SkyrampClient"` : ""}
+
+You MUST look for reusable patterns: authentication, HTTP helpers, data setup, validation, configuration, cleanup functions EXCLUDE current test file from the search.
+
+**STEP 2: IMPORT & REUSE (HIGHEST PRIORITY) - MANDATORY**
+You MUST import existing functions instead of duplicating. If you find reusable functions, you MUST import them:
+${language === "python"
+        ? `\`\`\`python
+from path.to.existing import helper_function
+from utils.auth_helpers import authenticate
+\`\`\``
+        : ""}
+
+${language === "typescript" || language === "javascript"
+        ? `\`\`\`typescript/javascript
+import { helperFunction } from './path/to/existing';
+import { authenticate } from './utils/authHelpers';
+\`\`\``
+        : ""}
+
+${language === "java"
+        ? `\`\`\`java
+import path.to.existing.helper_function;
+import utils.auth_helpers.authenticate;
+\`\`\``
+        : ""}
+
+if ${language === "python"
+        ? `IMPORTANT:
+FOR PYTHON:
+- If functions are in different folders, use relative path manipulation with os.path. NEVER hardcode absolute paths:
+  \`\`\`python
+  import sys
+  import os
+  # Add parent directory to path to access sibling folders
+  sys.path.append(os.path.dirname(os.path.dirname(__file__)))
+  from e2e.e2e_test import helper_function
+  
+  # OR if importing from same directory level
+  sys.path.append(os.path.dirname(__file__))
+  from e2e_test import helper_function
+  \`\`\`
+- Use aliases to avoid naming conflicts and prevent test execution:
+  \`\`\`python
+  # If importing a test file, use alias to prevent auto-execution
+  import e2e_test as e2e_helpers
+  # Then call: e2e_helpers.setup_auth_headers()
+  \`\`\`
+- CRITICAL: When importing test files, they may auto-execute. Use \`if __name__ == "__main__":\` guards in source files.
+  `
+        : ""}
+
+**STEP 3: REPLACE DUPLICATE CODE - MANDATORY**
+You MUST replace duplicate code with imported function calls. If you imported functions, you MUST use them.
+
+**STEP 4: CREATE MINIMAL NEW HELPERS (ONLY IF NEEDED)**
+Only if NO existing function can be reused:
+1. Group related lines logically (e.g., login steps together) to improve readability and parameterize the test function(s) with meaningful parameters to make it more flexible.
+2. If functions are already modularized (like breakpoint_section_0, breakpoint_section_1), then rename them with meaningful names WITHOUT ANY OTHER CHANGES.
+3. KEEP CHANGES TO A MINIMUM. DO NOT MODIFY THE FUNCTIONALITY OF THE TESTS. ONLY MODULARIZE THE CODE.
+4. Parameterize the test function(s) with meaningful parameters to make it more flexible. Preserve the original order of code lines within each function.
+5. Only extract reusable logical sections into helper functions or parameterized structures where applicable. Do not create any new test cases or a new modular file but only helper functions with modularization done in the same file. Do not add any new logic or classes or any other files.
+6. CRITICAL: DO NOT CHANGE THE FUNCTIONALITY OF THE TESTS. ONLY MODULARIZE THE CODE.
+
+**EXECUTION CHECKLIST - YOU MUST COMPLETE EACH:**
+- [ ] STEP 1: Searched for existing files using grep_search or file_search
+- [ ] STEP 2: Found reusable functions and imported them at the top of the file
+- [ ] STEP 3: Replaced duplicate code with imported function calls
+- [ ] STEP 4: Created minimal new helpers only where needed
+- [ ] Verified import paths are correct
+- [ ] Verified original functionality is maintained
+
+**CRITICAL: If you skip any step, the modularization is incomplete. You MUST complete all steps before proceeding.**
+
+**CRITICAL: FIX ERRORS IN MODULARIZED CODE USING skyramp_fix_errors TOOL**
+`;
+}
+export function getFixErrorsPrompt() {
+    return `
+**Fix errors in refactored code.**
+
+1. **Parameter Passing:** Identify functions using variables from outside scope (like Playwright 'page' object). Pass these as parameters.
+2. **Validate Correctness:** Ensure code is free of reference errors, undefined variables, runtime issues.
+3. **Import Paths:** Ensure import paths are correct and there are no circular imports.
+
+**KEY: Variables not defined within function scope MUST be passed as parameters.**
+`;
+}

package/build/prompts/startTraceCollectionPrompts.js

@@ -23,7 +23,10 @@ export function registerStartTraceCollectionPrompt(mcpServer) {
 
 **Example usage prompt for trace collection for playwright trace:**
 * To start a playwright trace collection session using agent, run the following command:
-  Start playwright trace collection with default settings.`,
+  Start playwright trace collection with default settings.
+
+**CRITICAL: FOR UI TESTS ALWAYS SHOW THE ABOVE PROMPT FOR PLAYWRIGHT TRACE COLLECTION. NEVER SHOW THE CLI COMMANDS.**
+`,
                 },
             },
         ],

package/build/prompts/testGenerationPrompt.js

@@ -14,6 +14,7 @@ export function registerTestGenerationPrompt(mcpServer) {
 - Guide users through test type selection and parameter collection
 - Provide clear execution instructions for generated tests
 - Answer questions about Skyramp capabilities and testing concepts
+- ALWAYS SHOW STEPS TO GENERATE TEST USING MCP TOOLS AND NEVER SHOW THE CLI COMMANDS.
 
 **CONTRACT TEST:**
 - Purpose: Ensures a service is properly communicating with another service
@@ -106,6 +107,8 @@ Let us generate a UI test with frontend playwright trace file skyramp_playwright
 
 **IMPORTANT:**
 - WHEN GENERATING TESTS USING TRACE, EXCLUDE THE PATHS THAT ARE NOT API ENDPOINTS.
+
+**CRITICAL: SHOW STEPS TO START/STOP PLAYWRIGHT TRACE COLLECTION FOR UI TESTS. NEVER SHOW THE CLI COMMANDS.**
             `,
                 },
             },

package/build/services/ModularizationService.js

@@ -1,4 +1,4 @@
-import { getModularizationPrompt } from "../utils/modularization-prompts.js";
+import { getModularizationPrompt } from "../prompts/modularization-prompts.js";
 export class ModularizationService {
     constructor() { }
     async processModularizationRequest(params) {
@@ -6,7 +6,7 @@ export class ModularizationService {
             content: [
                 {
                     type: "text",
-                    text: `${getModularizationPrompt()}`,
+                    text: `${getModularizationPrompt(params.testFile, params.language)}`,
                 },
             ],
         };

package/build/tools/executeSkyrampTestTool.js

@@ -4,13 +4,7 @@ import path from "path";
 import { Writable } from "stream";
 import { logger } from "../utils/logger.js";
 import { stripVTControlCharacters } from "util";
-// Configuration for language-specific file paths
-const LANGUAGE_PATHS = {
-    python: "/tmp",
-    javascript: "/tmp",
-    typescript: "/tmp",
-    java: "/app/src",
-};
+import fs from "fs";
 export function registerExecuteSkyrampTestTool(server) {
     server.registerTool("skyramp_execute_test", {
         description: `Execute a Skyramp-generated test in isolated containerized environments for reliable, deterministic testing.
@@ -39,6 +33,9 @@ IMPORTANT NOTES:
 
 For detailed documentation visit: https://www.skyramp.dev/docs/quickstart`,
         inputSchema: {
+            workspacePath: z
+                .string()
+                .describe("The path to the workspace directory where the test file is located"),
             language: z
                 .string()
                 .describe("Programming language of the test file to execute (e.g., python, javascript, typescript, java)"),
@@ -58,29 +55,34 @@ For detailed documentation visit: https://www.skyramp.dev/docs/quickstart`,
     }, async (params) => {
         var docker = new Docker();
         var image = "public.ecr.aws/skyramp/rampup/runner:mcp-v0.0.9";
+        const containerMountPath = "/home/user";
         // Use path.basename for safer filename extraction
         const filename = path.basename(params.testFile);
         if (!filename) {
             throw new Error("Invalid test file path: could not extract filename");
         }
-        // Use configurable language paths with fallback
-        const basePath = LANGUAGE_PATHS[params.language] || "/tmp";
-        const filePath = path.join(basePath, filename);
         const dockerSocketPath = "/var/run/docker.sock";
+        //remove workspace path from test file path
+        let testFilePath = path.relative(params.workspacePath, params.testFile);
+        testFilePath = path.resolve(containerMountPath, testFilePath);
         var command = [
             "./root/runner.sh",
             params.language,
-            filePath,
+            testFilePath,
             params.testType,
         ];
+        const workspacePath = path.resolve(params.workspacePath);
+        // check if workspace valid path
+        // Validate that the workspace path exists and is accessible
+        try {
+            fs.accessSync(workspacePath, fs.constants.R_OK);
+        }
+        catch (err) {
+            throw new Error(`Workspace path does not exist or is not readable: ${workspacePath}`);
+        }
         const hostConfig = {
             ExtraHosts: ["host.docker.internal:host-gateway"],
             Mounts: [
-                {
-                    Target: filePath,
-                    Source: path.resolve(params.testFile),
-                    Type: "bind",
-                },
                 {
                     Type: "bind",
                     Target: dockerSocketPath,
@@ -88,6 +90,16 @@ For detailed documentation visit: https://www.skyramp.dev/docs/quickstart`,
                 },
             ],
         };
+        //lets mount the files and directories inside the workspace path to the container and exclude package-lock.json, package.json and node_modules directory
+        const workspaceFiles = fs.readdirSync(workspacePath);
+        const filesToMount = workspaceFiles.filter((file) => file !== "package-lock.json" &&
+            file !== "package.json" &&
+            file !== "node_modules");
+        hostConfig.Mounts?.push(...filesToMount.map((file) => ({
+            Type: "bind",
+            Target: path.join(containerMountPath, file),
+            Source: path.join(workspacePath, file),
+        })));
         const env = [
             "SKYRAMP_TEST_TOKEN=" + params.token,
             "SKYRAMP_IN_DOCKER=true",

package/build/tools/fixErrorTool.js

@@ -1,6 +1,6 @@
 import { z } from "zod";
 import { logger } from "../utils/logger.js";
-import { getFixErrorsPrompt } from "../utils/modularization-prompts.js";
+import { getFixErrorsPrompt } from "../prompts/modularization-prompts.js";
 import { languageSchema } from "../types/TestTypes.js";
 import { getLanguageSteps } from "../utils/language-helper.js";
 const fixErrorSchema = z.object({

package/build/tools/generateContractRestTool.js

@@ -27,9 +27,7 @@ export function registerContractTestTool(server) {
     server.registerTool("skyramp_contract_test_generation", {
         description: `Generate a contract test using Skyramp's deterministic test generation platform.
 
-Contract tests ensure your API implementation matches its OpenAPI/Swagger specification exactly. They validate request/response schemas, status codes, headers, and data types to prevent contract violations and API breaking changes.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/contract-test`,
+Contract tests ensure your API implementation matches its OpenAPI/Swagger specification exactly. They validate request/response schemas, status codes, headers, and data types to prevent contract violations and API breaking changes.`,
         inputSchema: contractTestSchema,
     }, async (params) => {
         const service = new ContractTestService();

package/build/tools/generateE2ERestTool.js

@@ -30,9 +30,7 @@ export function registerE2ETestTool(server) {
 End-to-End tests validate complete user journeys by testing the entire application flow from frontend UI interactions to backend API responses. They ensure that all components work together correctly in realistic user scenarios, providing the highest confidence in application functionality.
 
 TRACE & UI INTEGRATION:
-E2E tests require both trace files (capturing backend API interactions) and Playwright recordings (capturing UI interactions) to generate comprehensive tests that validate the complete user experience.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/e2e-test`,
+E2E tests require both trace files (capturing backend API interactions) and Playwright recordings (capturing UI interactions) to generate comprehensive tests that validate the complete user experience.`,
         inputSchema: e2eTestSchema,
         annotations: {
             keywords: ["e2e test", "end-to-end test"],

package/build/tools/generateFuzzRestTool.js

@@ -23,9 +23,7 @@ export function registerFuzzTestTool(server) {
     server.registerTool("skyramp_fuzz_test_generation", {
         description: `Generate a fuzz test using Skyramp's deterministic test generation platform.
 
-Fuzz tests improve application security and reliability by sending invalid, malformed, or unexpected data to your API endpoints. They help discover edge cases, input validation issues, error handling problems, and potential security vulnerabilities.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/fuzz-test`,
+Fuzz tests improve application security and reliability by sending invalid, malformed, or unexpected data to your API endpoints. They help discover edge cases, input validation issues, error handling problems, and potential security vulnerabilities.`,
         inputSchema: fuzzTestSchema,
         annotations: {
             keywords: ["negative test", "random test"],

package/build/tools/generateIntegrationRestTool.js

@@ -29,9 +29,7 @@ export function registerIntegrationTestTool(server) {
     server.registerTool("skyramp_integration_test_generation", {
         description: `Generate an integration test using Skyramp's deterministic test generation platform.
 
-Integration tests validate that multiple services, components, or modules work together correctly. They test complex user workflows, service interactions, data flow between systems, and ensure that integrated components function as expected in realistic scenarios.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/integration-test`,
+Integration tests validate that multiple services, components, or modules work together correctly. They test complex user workflows, service interactions, data flow between systems, and ensure that integrated components function as expected in realistic scenarios.`,
         inputSchema: integrationTestSchema,
     }, async (params) => {
         const service = new IntegrationTestService();

package/build/tools/generateLoadRestTool.js

@@ -62,9 +62,7 @@ Load tests evaluate your application's performance, scalability, and stability u
 - IF THE USER DOES NOT PROVIDE LOAD PARAMETERS, THEN USE DEFAULT VALUES FOR LOAD TESTS:
   - loadDuration: "5" (5 seconds)
   - loadNumThreads: "1" (1 thread)
-  - Other load parameters should remain empty unless explicitly specified by the user
-
-For detailed documentation visit: https://www.skyramp.dev/docs/load-test/advanced-generation#start-trace-collection`,
+  - Other load parameters should remain empty unless explicitly specified by the user`,
         inputSchema: loadTestSchema,
         annotations: {
             keywords: ["load test", "performance test"],

package/build/tools/generateSmokeRestTool.js

@@ -23,9 +23,7 @@ export function registerSmokeTestTool(server) {
     server.registerTool("skyramp_smoke_test_generation", {
         description: `Generate a smoke test using Skyramp's deterministic test generation platform.
 
-Smoke testing is a preliminary check used to verify that an endpoint is accessible and returns a valid response. Smoke tests are useful for quickly identifying critical defects after significant changes. They provide rapid validation for basic functionality verification and endpoint accessibility testing.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/smoke-test`,
+Smoke testing is a preliminary check used to verify that an endpoint is accessible and returns a valid response. Smoke tests are useful for quickly identifying critical defects after significant changes. They provide rapid validation for basic functionality verification and endpoint accessibility testing.`,
         inputSchema: smokeTestSchema,
         annotations: {
             keywords: ["smoke test", "quick test"],

package/build/tools/generateUIRestTool.js

@@ -31,8 +31,7 @@ export function registerUITestTool(server) {
         description: `Generate a UI test using Skyramp's deterministic test generation platform.
       
 UI tests validate user interface functionality by simulating real user interactions with your web application. They test user workflows, form submissions, navigation, responsive design, and ensure that your frontend works correctly across different browsers and devices. UI tests use Playwright recordings as input to generate comprehensive test suites that replay user interactions, validate UI elements, and verify expected behaviors in browser environments.
-
-For detailed documentation visit: https://www.skyramp.dev/docs/ui-test`,
+**CRITICAL: USE TRACE COLLECTION START/STOP TOOLS FOR PLAYWRIGHT TRACE COLLECTION.**`,
         inputSchema: uiTestSchema,
         annotations: {
             keywords: ["ui test", "playwright"],

package/build/tools/modularizationTool.js

@@ -8,6 +8,7 @@ const modularizationSchema = {
     testFile: z
         .string()
         .describe("The test file to process with modularization principles applied"),
+    language: z.string().describe("The programming language of the test file"),
 };
 export function registerModularizationTool(server) {
     server.registerTool("skyramp_modularization", {
@@ -24,8 +25,9 @@ export function registerModularizationTool(server) {
         },
     }, async (params) => {
         logger.info("Generating modularization", {
-            prompt: params.prompt,
             testFile: params.testFile,
+            language: params.language,
+            prompt: params.prompt,
         });
         const service = new ModularizationService();
         return await service.processModularizationRequest(params);

package/build/tools/stopTraceCollectionTool.js

@@ -1,8 +1,11 @@
 import { SkyrampClient } from "@skyramp/skyramp";
 import { closeProxyTerminal } from "../utils/proxy-terminal.js";
 import { z } from "zod";
-import { PLAYWRIGHT_OUTPUT_FILE_FIELD_NAME, TELEMETRY_entrypoint_FIELD_NAME, TRACE_OUTPUT_FILE_FIELD_NAME, validatePath, } from "../utils/utils.js";
+import { TELEMETRY_entrypoint_FIELD_NAME, } from "../utils/utils.js";
 import { logger } from "../utils/logger.js";
+import { baseSchema } from "../types/TestTypes.js";
+import path from "path";
+import { existsSync, mkdirSync } from "fs";
 export function registerTraceStopTool(server) {
     server.registerTool("skyramp_stop_trace_collection", {
         description: `Stop trace collection and save captured data using Skyramp's comprehensive tracing capabilities.
@@ -20,13 +23,14 @@ For detailed documentation visit: https://www.skyramp.dev/docs/load-test/advance
         inputSchema: {
             traceOutputFile: z
                 .string()
-                .describe("MUST be absolute path to save the trace output file (e.g., /path/to/skyramp-traces.json). This file will contain the collected trace data"),
-            playwright: z
+                .describe("File name to save the trace output file (e.g., skyramp-traces.json). This file will contain the collected backend trace data"),
+            playwrightEnabled: z
                 .boolean()
                 .describe("Whether Playwright was used for trace collection. Must match the setting used when starting trace collection"),
             playwrightOutput: z
                 .string()
-                .describe("MUST be absolute path to save the Playwright output file (e.g., /path/to/playwright.zip). Only used when playwright is true"),
+                .describe("File name to save the Playwright output file (e.g., playwright.zip). Only used when playwright is true"),
+            outputDir: baseSchema.shape.outputDir,
             prompt: z
                 .string()
                 .describe("The prompt user provided to stop trace collection"),
@@ -37,7 +41,7 @@ For detailed documentation visit: https://www.skyramp.dev/docs/load-test/advance
     }, async (params) => {
         logger.info("Stopping trace collection", {
             traceOutputFile: params.traceOutputFile,
-            playwright: params.playwright,
+            playwright: params.playwrightEnabled,
             playwrightOutput: params.playwrightOutput,
             prompt: params.prompt,
         });
@@ -46,10 +50,20 @@ For detailed documentation visit: https://www.skyramp.dev/docs/load-test/advance
             const stopTraceOptions = {
                 output: params.traceOutputFile ?? "skyramp-traces.json",
                 workerContainerName: "skyramp-trace-worker",
-                playwright: params.playwright ?? false,
+                playwright: params.playwrightEnabled ?? false,
                 playwrightOutput: params.playwrightOutput ?? "playwright.zip",
                 entrypoint: TELEMETRY_entrypoint_FIELD_NAME,
+                outputDir: params.outputDir,
             };
+            // Check if output dir exists and if not create it.
+            if (!existsSync(params.outputDir)) {
+                mkdirSync(params.outputDir, { recursive: true });
+            }
+            // Temporary fix until library is updated
+            if (params.outputDir) {
+                params.traceOutputFile = path.join(params.outputDir, params.traceOutputFile);
+                params.playwrightOutput = path.join(params.outputDir, params.playwrightOutput);
+            }
             let errList = {
                 content: [],
                 isError: true,
@@ -68,14 +82,6 @@ For detailed documentation visit: https://www.skyramp.dev/docs/load-test/advance
                 logger.info("Playwright disabled for trace collection");
                 stopTraceOptions.playwrightOutput = "";
             }
-            let err = validatePath(stopTraceOptions.output, TRACE_OUTPUT_FILE_FIELD_NAME);
-            if (err && err.content) {
-                errList.content.push(err.content[0]);
-            }
-            err = validatePath(stopTraceOptions.playwrightOutput, PLAYWRIGHT_OUTPUT_FILE_FIELD_NAME);
-            if (err && err.content) {
-                errList.content.push(err.content[0]);
-            }
             // If error is not empty, return error
             if (errList.content.length > 0) {
                 return errList;

package/build/utils/language-helper.js

@@ -78,7 +78,7 @@ java -jar "./lib/junit-platform-console-standalone-\${JUNIT_PLATFORM_VER}.jar" \
 }
 function appendExecutionInstruction() {
     return `
-- Notify the user that they can also use ** Execute with Skyramp ** tool to run the test.If this is your first test you are trying to execute with Skyramp, it may take a little bit longer than usual.
+- Notify the user that they can also use ** Execute with Skyramp ** tool to run the test.If this is your first test you are trying to execute with Skyramp, it may take a little bit longer than usual because we need to build the image for the first time.
 - Before I can execute the test for you, I need to confirm the following information:
   Authentication: Please provide me with your authentication token (by default we assume a Bearer Token). If you don't require any token for your service please just say: 'No token required'
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.0.17",
+  "version": "0.0.19",
   "main": "build/index.js",
   "type": "module",
   "bin": {

package/build/resources/modulazrizationInstructions.js

@@ -1,15 +0,0 @@
-import { getFixErrorsPrompt, getModularizationPrompt, } from "../utils/modularization-prompts.js";
-export function registerModularizationInstructions(mcpServer) {
-    mcpServer.resource("modularization_instructions", "mcp://modularization_instructions", async () => ({
-        contents: [
-            {
-                uri: "mcp://modularization_instructions",
-                mimeType: "text/markdown",
-                text: `
-${getModularizationPrompt()}
-${getFixErrorsPrompt()}
-        `,
-            },
-        ],
-    }));
-}

package/build/utils/modularization-prompts.js

@@ -1,23 +0,0 @@
-export function getModularizationPrompt() {
-    return `
-**CRITICAL: Please refactor the code with these modularization principles. Respond with the complete, modularized code only in the same file WITHOUT ANY ERRORS**
-
-1. Group related lines logically (e.g., login steps together) to improve readability and parameterize the test function(s) with meaningful parameters to make it more flexible.
-2. If functions are already modularized (like breakpoint_section_0, breakpoint_section_1), then rename them with meaningful names WITHOUT ANY OTHER CHANGES.
-3. KEEP CHANGES TO A MINIMUM. DO NOT MODIFY THE FUNCTIONALITY OF THE TESTS. ONLY MODULARIZE THE CODE.
-4. Parameterize the test function(s) with meaningful parameters to make it more flexible. Preserve the original order of code lines within each function.
-5. Only extract reusable logical sections into helper functions or parameterized structures where applicable. Do not create any new test cases or a new modular file but only helper functions with modularization done in the same file. Do not add any new logic or classes or any other files.
-
-CRITICAL: FIX ERRORS IN THE MODULARIZED CODE USING skyramp_fix_errors TOOL
-`;
-}
-export function getFixErrorsPrompt() {
-    return `
-**Fix errors in the refactored code.**
-
-1. **Parameter Passing:** Carefully examine the code. Identify all functions that use variables defined outside their own scope (like a Playwright 'page' object or a shared configuration).
-2. **Validate Correctness:** Ensure the final code is free of any reference errors, undefined variables, or other runtime issues. The code must be ready to execute.
-
-**REMEMBER: The key insight is that if a function references any variable that's not defined within its scope, that variable MUST be passed as a parameter. The "page" object is the most common culprit in Playwright tests.**
-`;
-}