codeguard-testgen 1.0.7 → 1.0.9

package/dist/promptService.js

@@ -1,173 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-const mongodb_1 = require("mongodb");
-const prompts_1 = require("./prompts");
-class PromptService {
-    constructor() {
-        this.client = null;
-        this.db = null;
-        this.cache = new Map();
-        this.CACHE_TTL = 5 * 60 * 1000; // 5 minutes
-        this.CONNECTION_TIMEOUT = 2000; // 2 seconds
-        this.mongoUri = null;
-        this.enabled = true;
-        this.connectionAttempted = false;
-    }
-    /**
-     * Initialize the prompt service with MongoDB configuration
-     */
-    async initialize(mongoUri, enabled = true) {
-        this.enabled = enabled;
-        this.mongoUri = mongoUri || null;
-        // Don't connect immediately, connect on first use
-    }
-    /**
-     * Ensure MongoDB connection is established
-     */
-    async ensureConnection() {
-        if (this.db) {
-            return true;
-        }
-        if (this.connectionAttempted) {
-            return false;
-        }
-        if (!this.mongoUri || !this.enabled) {
-            return false;
-        }
-        this.connectionAttempted = true;
-        try {
-            const connectionPromise = mongodb_1.MongoClient.connect(this.mongoUri, {
-                serverSelectionTimeoutMS: this.CONNECTION_TIMEOUT,
-                connectTimeoutMS: this.CONNECTION_TIMEOUT,
-            });
-            // Add timeout wrapper
-            const timeoutPromise = new Promise((_, reject) => setTimeout(() => reject(new Error('Connection timeout')), this.CONNECTION_TIMEOUT));
-            this.client = await Promise.race([connectionPromise, timeoutPromise]);
-            this.db = this.client.db();
-            return true;
-        }
-        catch (error) {
-            return false;
-        }
-    }
-    /**
-     * Get cache key for a prompt
-     */
-    getCacheKey(promptType, provider) {
-        return `${promptType}:${provider}`;
-    }
-    /**
-     * Check if cached prompt is still valid
-     */
-    isCacheValid(cacheKey) {
-        const cached = this.cache.get(cacheKey);
-        if (!cached) {
-            return false;
-        }
-        const age = Date.now() - cached.timestamp;
-        return age < this.CACHE_TTL;
-    }
-    /**
-     * Fetch prompt from MongoDB
-     */
-    async fetchFromMongoDB(promptType, provider) {
-        if (!await this.ensureConnection() || !this.db) {
-            return null;
-        }
-        try {
-            const collection = this.db.collection('prompts');
-            const queryPromise = collection.findOne({
-                promptType,
-                provider,
-                isActive: true
-            }, {
-                sort: { updatedAt: -1 }
-            });
-            // Add timeout to query
-            const timeoutPromise = new Promise((_, reject) => setTimeout(() => reject(new Error('Query timeout')), this.CONNECTION_TIMEOUT));
-            const document = await Promise.race([queryPromise, timeoutPromise]);
-            if (document && document.content) {
-                return document.content;
-            }
-            return null;
-        }
-        catch (error) {
-            return null;
-        }
-    }
-    /**
-     * Get fallback prompt from hardcoded prompts
-     */
-    getFallbackPrompt(promptType, provider) {
-        const prompts = promptType === 'file-wise' ? prompts_1.FILEWISE_PROMPTS : prompts_1.FUNCTIONWISE_PROMPTS;
-        return prompts[provider];
-    }
-    /**
-     * Get prompt with three-tier priority system:
-     * 1. User's custom prompt (from codeguard.json)
-     * 2. Remote MongoDB prompt (maintainer's centralized prompts)
-     * 3. Fallback prompt (hardcoded in package)
-     */
-    async getPrompt(promptType, provider, customPrompts) {
-        // Priority 1: Check for user's custom prompt in their config
-        if (customPrompts) {
-            const customPromptKey = promptType === 'file-wise' ? 'fileWise' : 'functionWise';
-            const userPrompt = customPrompts[customPromptKey]?.[provider];
-            if (userPrompt && userPrompt.trim() !== '') {
-                console.log(`📝 Using custom prompt`);
-                return userPrompt;
-            }
-        }
-        const cacheKey = this.getCacheKey(promptType, provider);
-        // Check cache for MongoDB/fallback prompts
-        if (this.isCacheValid(cacheKey)) {
-            const cached = this.cache.get(cacheKey);
-            if (cached) {
-                return cached.content;
-            }
-        }
-        // Priority 2: Try to fetch from MongoDB (maintainer's database)
-        if (this.enabled && this.mongoUri) {
-            const remotePrompt = await this.fetchFromMongoDB(promptType, provider);
-            if (remotePrompt) {
-                console.log(`📝 Using remote prompt`);
-                // Cache the fetched prompt
-                this.cache.set(cacheKey, {
-                    content: remotePrompt,
-                    timestamp: Date.now()
-                });
-                return remotePrompt;
-            }
-        }
-        // Priority 3: Fallback to hardcoded prompt
-        console.log(`📝 Using fallback prompt`);
-        const fallbackPrompt = this.getFallbackPrompt(promptType, provider);
-        // Cache the fallback prompt too
-        this.cache.set(cacheKey, {
-            content: fallbackPrompt,
-            timestamp: Date.now()
-        });
-        return fallbackPrompt;
-    }
-    /**
-     * Clear the prompt cache
-     */
-    clearCache() {
-        this.cache.clear();
-    }
-    /**
-     * Close MongoDB connection
-     */
-    async close() {
-        if (this.client) {
-            await this.client.close();
-            this.client = null;
-            this.db = null;
-            this.connectionAttempted = false;
-        }
-    }
-}
-// Singleton instance
-const promptService = new PromptService();
-exports.default = promptService;
-//# sourceMappingURL=promptService.js.map

package/dist/promptService.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"promptService.js","sourceRoot":"","sources":["../src/promptService.ts"],"names":[],"mappings":";;AAAA,qCAAsD;AACtD,uCAAmE;AAqBnE,MAAM,aAAa;IAAnB;QACU,WAAM,GAAuB,IAAI,CAAC;QAClC,OAAE,GAAc,IAAI,CAAC;QACrB,UAAK,GAA6B,IAAI,GAAG,EAAE,CAAC;QACnC,cAAS,GAAG,CAAC,GAAG,EAAE,GAAG,IAAI,CAAC,CAAC,YAAY;QACvC,uBAAkB,GAAG,IAAI,CAAC,CAAC,YAAY;QAChD,aAAQ,GAAkB,IAAI,CAAC;QAC/B,YAAO,GAAY,IAAI,CAAC;QACxB,wBAAmB,GAAY,KAAK,CAAC;IAqM/C,CAAC;IAnMC;;OAEG;IACH,KAAK,CAAC,UAAU,CAAC,QAA4B,EAAE,UAAmB,IAAI;QACpE,IAAI,CAAC,OAAO,GAAG,OAAO,CAAC;QACvB,IAAI,CAAC,QAAQ,GAAG,QAAQ,IAAI,IAAI,CAAC;QAEjC,kDAAkD;IACpD,CAAC;IAED;;OAEG;IACK,KAAK,CAAC,gBAAgB;QAC5B,IAAI,IAAI,CAAC,EAAE,EAAE,CAAC;YACZ,OAAO,IAAI,CAAC;QACd,CAAC;QAED,IAAI,IAAI,CAAC,mBAAmB,EAAE,CAAC;YAC7B,OAAO,KAAK,CAAC;QACf,CAAC;QAED,IAAI,CAAC,IAAI,CAAC,QAAQ,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,CAAC;YACpC,OAAO,KAAK,CAAC;QACf,CAAC;QAED,IAAI,CAAC,mBAAmB,GAAG,IAAI,CAAC;QAEhC,IAAI,CAAC;YACH,MAAM,iBAAiB,GAAG,qBAAW,CAAC,OAAO,CAAC,IAAI,CAAC,QAAQ,EAAE;gBAC3D,wBAAwB,EAAE,IAAI,CAAC,kBAAkB;gBACjD,gBAAgB,EAAE,IAAI,CAAC,kBAAkB;aAC1C,CAAC,CAAC;YAEH,sBAAsB;YACtB,MAAM,cAAc,GAAG,IAAI,OAAO,CAAQ,CAAC,CAAC,EAAE,MAAM,EAAE,EAAE,CACtD,UAAU,CAAC,GAAG,EAAE,CAAC,MAAM,CAAC,IAAI,KAAK,CAAC,oBAAoB,CAAC,CAAC,EAAE,IAAI,CAAC,kBAAkB,CAAC,CACnF,CAAC;YAEF,IAAI,CAAC,MAAM,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,iBAAiB,EAAE,cAAc,CAAC,CAAC,CAAC;YACtE,IAAI,CAAC,EAAE,GAAG,IAAI,CAAC,MAAM,CAAC,EAAE,EAAE,CAAC;YAE3B,OAAO,IAAI,CAAC;QACd,CAAC;QAAC,OAAO,KAAU,EAAE,CAAC;YACpB,OAAO,KAAK,CAAC;QACf,CAAC;IACH,CAAC;IAED;;OAEG;IACK,WAAW,CAAC,UAAsB,EAAE,QAAoB;QAC9D,OAAO,GAAG,UAAU,IAAI,QAAQ,EAAE,CAAC;IACrC,CAAC;IAED;;OAEG;IACK,YAAY,CAAC,QAAgB;QACnC,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QACxC,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,OAAO,KAAK,CAAC;QACf,CAAC;QAED,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,GAAG,MAAM,CAAC,SAAS,CAAC;QAC1C,OAAO,GAAG,GAAG,IAAI,CAAC,SAAS,CAAC;IAC9B,CAAC;IAED;;OAEG;IACK,KAAK,CAAC,gBAAgB,CAC5B,UAAsB,EACtB,QAAoB;QAEpB,IAAI,CAAC,MAAM,IAAI,CAAC,gBAAgB,EAAE,IAAI,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC;YAC/C,OAAO,IAAI,CAAC;QACd,CAAC;QAED,IAAI,CAAC;YACH,MAAM,UAAU,GAA+B,IAAI,CAAC,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC;YAE7E,MAAM,YAAY,GAAG,UAAU,CAAC,OAAO,CAAC;gBACtC,UAAU;gBACV,QAAQ;gBACR,QAAQ,EAAE,IAAI;aACf,EAAE;gBACD,IAAI,EAAE,EAAE,SAAS,EAAE,CAAC,CAAC,EAAE;aACxB,CAAC,CAAC;YAEH,uBAAuB;YACvB,MAAM,cAAc,GAAG,IAAI,OAAO,CAAQ,CAAC,CAAC,EAAE,MAAM,EAAE,EAAE,CACtD,UAAU,CAAC,GAAG,EAAE,CAAC,MAAM,CAAC,IAAI,KAAK,CAAC,eAAe,CAAC,CAAC,EAAE,IAAI,CAAC,kBAAkB,CAAC,CAC9E,CAAC;YAEF,MAAM,QAAQ,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,YAAY,EAAE,cAAc,CAAC,CAAC,CAAC;YAEpE,IAAI,QAAQ,IAAI,QAAQ,CAAC,OAAO,EAAE,CAAC;gBACjC,OAAO,QAAQ,CAAC,OAAO,CAAC;YAC1B,CAAC;YAED,OAAO,IAAI,CAAC;QACd,CAAC;QAAC,OAAO,KAAU,EAAE,CAAC;YACpB,OAAO,IAAI,CAAC;QACd,CAAC;IACH,CAAC;IAED;;OAEG;IACK,iBAAiB,CAAC,UAAsB,EAAE,QAAoB;QACpE,MAAM,OAAO,GAAG,UAAU,KAAK,WAAW,CAAC,CAAC,CAAC,0BAAgB,CAAC,CAAC,CAAC,8BAAoB,CAAC;QACrF,OAAO,OAAO,CAAC,QAAQ,CAAC,CAAC;IAC3B,CAAC;IAED;;;;;OAKG;IACH,KAAK,CAAC,SAAS,CACb,UAAsB,EACtB,QAAoB,EACpB,aAGC;QAED,6DAA6D;QAC7D,IAAI,aAAa,EAAE,CAAC;YAClB,MAAM,eAAe,GAAG,UAAU,KAAK,WAAW,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,cAAc,CAAC;YACjF,MAAM,UAAU,GAAG,aAAa,CAAC,eAAe,CAAC,EAAE,CAAC,QAAQ,CAAC,CAAC;YAE9D,IAAI,UAAU,IAAI,UAAU,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC;gBAC3C,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC;gBACtC,OAAO,UAAU,CAAC;YACpB,CAAC;QACH,CAAC;QAED,MAAM,QAAQ,GAAG,IAAI,CAAC,WAAW,CAAC,UAAU,EAAE,QAAQ,CAAC,CAAC;QAExD,2CAA2C;QAC3C,IAAI,IAAI,CAAC,YAAY,CAAC,QAAQ,CAAC,EAAE,CAAC;YAChC,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;YACxC,IAAI,MAAM,EAAE,CAAC;gBACX,OAAO,MAAM,CAAC,OAAO,CAAC;YACxB,CAAC;QACH,CAAC;QAED,gEAAgE;QAChE,IAAI,IAAI,CAAC,OAAO,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YAClC,MAAM,YAAY,GAAG,MAAM,IAAI,CAAC,gBAAgB,CAAC,UAAU,EAAE,QAAQ,CAAC,CAAC;YACvE,IAAI,YAAY,EAAE,CAAC;gBACjB,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC;gBACtC,2BAA2B;gBAC3B,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,EAAE;oBACvB,OAAO,EAAE,YAAY;oBACrB,SAAS,EAAE,IAAI,CAAC,GAAG,EAAE;iBACtB,CAAC,CAAC;gBACH,OAAO,YAAY,CAAC;YACtB,CAAC;QACH,CAAC;QAED,2CAA2C;QAC3C,OAAO,CAAC,GAAG,CAAC,0BAA0B,CAAC,CAAC;QACxC,MAAM,cAAc,GAAG,IAAI,CAAC,iBAAiB,CAAC,UAAU,EAAE,QAAQ,CAAC,CAAC;QAEpE,gCAAgC;QAChC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,QAAQ,EAAE;YACvB,OAAO,EAAE,cAAc;YACvB,SAAS,EAAE,IAAI,CAAC,GAAG,EAAE;SACtB,CAAC,CAAC;QAEH,OAAO,cAAc,CAAC;IACxB,CAAC;IAED;;OAEG;IACH,UAAU;QACR,IAAI,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC;IACrB,CAAC;IAED;;OAEG;IACH,KAAK,CAAC,KAAK;QACT,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;YAChB,MAAM,IAAI,CAAC,MAAM,CAAC,KAAK,EAAE,CAAC;YAC1B,IAAI,CAAC,MAAM,GAAG,IAAI,CAAC;YACnB,IAAI,CAAC,EAAE,GAAG,IAAI,CAAC;YACf,IAAI,CAAC,mBAAmB,GAAG,KAAK,CAAC;QACnC,CAAC;IACH,CAAC;CACF;AAED,qBAAqB;AACrB,MAAM,aAAa,GAAG,IAAI,aAAa,EAAE,CAAC;AAE1C,kBAAe,aAAa,CAAC"}

package/dist/prompts.d.ts

@@ -1,12 +0,0 @@
-/**
- * Fallback prompts for AI test generation
- * These are used when MongoDB is not configured or unavailable
- */
-export interface PromptTemplates {
-    claude: string;
-    openai: string;
-    gemini: string;
-}
-export declare const FILEWISE_PROMPTS: PromptTemplates;
-export declare const FUNCTIONWISE_PROMPTS: PromptTemplates;
-//# sourceMappingURL=prompts.d.ts.map

package/dist/prompts.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,WAAW,eAAe;IAC9B,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,MAAM,CAAC;CAChB;AAGD,eAAO,MAAM,gBAAgB,EAAE,eAgS9B,CAAC;AAGF,eAAO,MAAM,oBAAoB,EAAE,eA8KlC,CAAC"}

package/dist/prompts.js

@@ -1,470 +0,0 @@
-"use strict";
-/**
- * Fallback prompts for AI test generation
- * These are used when MongoDB is not configured or unavailable
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.FUNCTIONWISE_PROMPTS = exports.FILEWISE_PROMPTS = void 0;
-// File-wise test generation prompts (default prompt used for all providers as fallback)
-exports.FILEWISE_PROMPTS = {
-    claude: `You are a senior software engineer tasked with writing comprehensive Jest unit tests including edge cases for a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get a complete AST analysis of the source file (functions, classes, types, exports)
-2. Use get_imports_ast tool to understand all dependencies
-3. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths for the test file
-4. For complex functions, use get_function_ast tool to get detailed information including parameters, return types, and cyclomatic complexity
-5. For classes, use get_class_methods tool to extract all methods
-6. Use get_type_definitions tool to understand TypeScript types and interfaces
-7. Generate comprehensive Jest unit tests with:
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules like '../database' or '../database/index' 
-   - Mock models, services, and any modules that access config/database
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each function/class
-   - REQUIRED: Test cases should include security and input validation tests.
-   - REQUIRED: Multiple test cases covering:
-     * Happy path scenarios  
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-8. REQUIRED: Write the COMPLETE test file using write_test_file tool with REAL test code (NOT placeholders!)
-   - CRITICAL: Include source_file parameter with path to source file (e.g., source_file: "{{sourceFile}}")
-   - DO NOT use ANY placeholder comments like:
-     * "// Mock setup", "// Assertions", "// Call function"  
-     * "// Further tests...", "// Additional tests..."  
-     * "// Similarly, write tests for..."
-     * "// Add more tests...", "// TODO", "// ..."
-   - Write ACTUAL working test code with real mocks, real assertions, real function calls
-   - Every test MUST have:
-     * Real setup code (mock functions, create test data)
-     * Real execution (call the function being tested)
-     * Real expect() assertions (at least one per test)
-   - Write tests for EVERY exported function (minimum 3-5 tests per function)
-   - If source has 4 functions, test file MUST have 4 describe blocks with actual tests
-   - Example of COMPLETE test structure:
-     * Setup: Create mocks and test data
-     * Execute: Call the function being tested  
-     * Assert: Use expect() to verify results
-9. REQUIRED: Run the tests using run_tests tool
-10. REQUIRED: If tests fail with import errors:
-    - Use find_file tool to locate the missing module
-    - Use calculate_relative_path tool to get correct import path
-    - PRIMARY METHOD (once test file exists): Use line-based editing:
-      * read_file to get current test file with line numbers
-      * insert_lines to add missing imports at correct position (e.g., line 3)
-      * delete_lines to remove incorrect imports
-      * replace_lines to fix import paths
-    - FALLBACK: Only use edit_test_file or write_test_file if line-based editing isn't suitable
-11. REQUIRED: If tests fail with other errors, analyze if they are FIXABLE or LEGITIMATE:
-    
-    FIXABLE ERRORS (you should fix these):
-    - Wrong import paths
-    - Missing mocks
-    - Incorrect mock implementations
-    - Wrong assertions or test logic
-    - TypeScript compilation errors
-    - Missing test setup/teardown
-    - Cannot read properties of undefined
-    
-    LEGITIMATE FAILURES (source code bugs - DO NOT try to fix):
-    - Function returns wrong type (e.g., undefined instead of object)
-    - Missing null/undefined checks in source code
-    - Logic errors in source code
-    - Unhandled promise rejections in source code
-    - Source code throws unexpected errors
-    
-12. If errors are FIXABLE (AFTER test file is written): 
-    - ✅ PRIMARY METHOD: Use line-based editing tools (RECOMMENDED):
-      * read_file to get current test file with line numbers
-      * delete_lines to remove incorrect lines
-      * insert_lines to add missing code (e.g., mocks, imports)
-      * replace_lines to fix specific line ranges
-      * This is FASTER and MORE RELIABLE than rewriting entire file!
-    - ⚠️ FALLBACK: Only use edit_test_file or write_test_file if:
-      * Line-based editing is too complex (needs major restructuring)
-      * Multiple scattered changes across the file
-    - Then retry running tests
-13. If errors are LEGITIMATE: Call report_legitimate_failure tool with details and STOP trying to fix
-    - Provide failing test names, reason, and source code issue description
-    - The test file will be kept as-is with legitimate failing tests
-14. REQUIRED: Repeat steps 9-13 until tests pass OR legitimate failures are reported
-15. REQUIRED: Ensure all functions are tested in the test file.
-
-CRITICAL: Distinguish between test bugs (fix them) and source code bugs (report and stop)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`,
-    openai: `You are a senior software engineer tasked with writing comprehensive Jest unit tests including edge cases for a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get a complete AST analysis of the source file (functions, classes, types, exports)
-2. Use get_imports_ast tool to understand all dependencies
-3. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths for the test file
-4. For complex functions, use get_function_ast tool to get detailed information including parameters, return types, and cyclomatic complexity
-5. For classes, use get_class_methods tool to extract all methods
-6. Use get_type_definitions tool to understand TypeScript types and interfaces
-7. Generate comprehensive Jest unit tests with:
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules like '../database' or '../database/index' 
-   - Mock models, services, and any modules that access config/database
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each function/class
-   - REQUIRED: Test cases should include security and input validation tests.
-   - REQUIRED: Multiple test cases covering:
-     * Happy path scenarios  
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-8. REQUIRED: Write the COMPLETE test file using write_test_file tool with REAL test code (NOT placeholders!)
-   - CRITICAL: Include source_file parameter with path to source file (e.g., source_file: "{{sourceFile}}")
-   - DO NOT use ANY placeholder comments like:
-     * "// Mock setup", "// Assertions", "// Call function"  
-     * "// Further tests...", "// Additional tests..."  
-     * "// Similarly, write tests for..."
-     * "// Add more tests...", "// TODO", "// ..."
-   - Write ACTUAL working test code with real mocks, real assertions, real function calls
-   - Every test MUST have:
-     * Real setup code (mock functions, create test data)
-     * Real execution (call the function being tested)
-     * Real expect() assertions (at least one per test)
-   - Write tests for EVERY exported function (minimum 3-5 tests per function)
-   - If source has 4 functions, test file MUST have 4 describe blocks with actual tests
-   - Example of COMPLETE test structure:
-     * Setup: Create mocks and test data
-     * Execute: Call the function being tested  
-     * Assert: Use expect() to verify results
-9. REQUIRED: Run the tests using run_tests tool
-10. REQUIRED: If tests fail with import errors:
-    - Use find_file tool to locate the missing module
-    - Use calculate_relative_path tool to get correct import path
-    - PRIMARY METHOD (once test file exists): Use line-based editing:
-      * read_file to get current test file with line numbers
-      * insert_lines to add missing imports at correct position (e.g., line 3)
-      * delete_lines to remove incorrect imports
-      * replace_lines to fix import paths
-    - FALLBACK: Only use edit_test_file or write_test_file if line-based editing isn't suitable
-11. REQUIRED: If tests fail with other errors, analyze if they are FIXABLE or LEGITIMATE:
-    
-    FIXABLE ERRORS (you should fix these):
-    - Wrong import paths
-    - Missing mocks
-    - Incorrect mock implementations
-    - Wrong assertions or test logic
-    - TypeScript compilation errors
-    - Missing test setup/teardown
-    - Cannot read properties of undefined
-    
-    LEGITIMATE FAILURES (source code bugs - DO NOT try to fix):
-    - Function returns wrong type (e.g., undefined instead of object)
-    - Missing null/undefined checks in source code
-    - Logic errors in source code
-    - Unhandled promise rejections in source code
-    - Source code throws unexpected errors
-    
-12. If errors are FIXABLE (AFTER test file is written): 
-    - ✅ PRIMARY METHOD: Use line-based editing tools (RECOMMENDED):
-      * read_file to get current test file with line numbers
-      * delete_lines to remove incorrect lines
-      * insert_lines to add missing code (e.g., mocks, imports)
-      * replace_lines to fix specific line ranges
-      * This is FASTER and MORE RELIABLE than rewriting entire file!
-    - ⚠️ FALLBACK: Only use edit_test_file or write_test_file if:
-      * Line-based editing is too complex (needs major restructuring)
-      * Multiple scattered changes across the file
-    - Then retry running tests
-13. If errors are LEGITIMATE: Call report_legitimate_failure tool with details and STOP trying to fix
-    - Provide failing test names, reason, and source code issue description
-    - The test file will be kept as-is with legitimate failing tests
-14. REQUIRED: Repeat steps 9-13 until tests pass OR legitimate failures are reported
-15. REQUIRED: Ensure all functions are tested in the test file.
-
-CRITICAL: Distinguish between test bugs (fix them) and source code bugs (report and stop)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`,
-    gemini: `You are a senior software engineer tasked with writing comprehensive Jest unit tests including edge cases for a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get a complete AST analysis of the source file (functions, classes, types, exports)
-2. Use get_imports_ast tool to understand all dependencies
-3. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths for the test file
-4. For complex functions, use get_function_ast tool to get detailed information including parameters, return types, and cyclomatic complexity
-5. For classes, use get_class_methods tool to extract all methods
-6. Use get_type_definitions tool to understand TypeScript types and interfaces
-7. Generate comprehensive Jest unit tests with:
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules like '../database' or '../database/index' 
-   - Mock models, services, and any modules that access config/database
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each function/class
-   - REQUIRED: Test cases should include security and input validation tests.
-   - REQUIRED: Multiple test cases covering:
-     * Happy path scenarios  
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-8. REQUIRED: Write the COMPLETE test file using write_test_file tool with REAL test code (NOT placeholders!)
-   - CRITICAL: Include source_file parameter with path to source file (e.g., source_file: "{{sourceFile}}")
-   - DO NOT use ANY placeholder comments like:
-     * "// Mock setup", "// Assertions", "// Call function"  
-     * "// Further tests...", "// Additional tests..."  
-     * "// Similarly, write tests for..."
-     * "// Add more tests...", "// TODO", "// ..."
-   - Write ACTUAL working test code with real mocks, real assertions, real function calls
-   - Every test MUST have:
-     * Real setup code (mock functions, create test data)
-     * Real execution (call the function being tested)
-     * Real expect() assertions (at least one per test)
-   - Write tests for EVERY exported function (minimum 3-5 tests per function)
-   - If source has 4 functions, test file MUST have 4 describe blocks with actual tests
-   - Example of COMPLETE test structure:
-     * Setup: Create mocks and test data
-     * Execute: Call the function being tested  
-     * Assert: Use expect() to verify results
-9. REQUIRED: Run the tests using run_tests tool
-10. REQUIRED: If tests fail with import errors:
-    - Use find_file tool to locate the missing module
-    - Use calculate_relative_path tool to get correct import path
-    - PRIMARY METHOD (once test file exists): Use line-based editing:
-      * read_file to get current test file with line numbers
-      * insert_lines to add missing imports at correct position (e.g., line 3)
-      * delete_lines to remove incorrect imports
-      * replace_lines to fix import paths
-    - FALLBACK: Only use edit_test_file or write_test_file if line-based editing isn't suitable
-11. REQUIRED: If tests fail with other errors, analyze if they are FIXABLE or LEGITIMATE:
-    
-    FIXABLE ERRORS (you should fix these):
-    - Wrong import paths
-    - Missing mocks
-    - Incorrect mock implementations
-    - Wrong assertions or test logic
-    - TypeScript compilation errors
-    - Missing test setup/teardown
-    - Cannot read properties of undefined
-    
-    LEGITIMATE FAILURES (source code bugs - DO NOT try to fix):
-    - Function returns wrong type (e.g., undefined instead of object)
-    - Missing null/undefined checks in source code
-    - Logic errors in source code
-    - Unhandled promise rejections in source code
-    - Source code throws unexpected errors
-    
-12. If errors are FIXABLE (AFTER test file is written): 
-    - ✅ PRIMARY METHOD: Use line-based editing tools (RECOMMENDED):
-      * read_file to get current test file with line numbers
-      * delete_lines to remove incorrect lines
-      * insert_lines to add missing code (e.g., mocks, imports)
-      * replace_lines to fix specific line ranges
-      * This is FASTER and MORE RELIABLE than rewriting entire file!
-    - ⚠️ FALLBACK: Only use edit_test_file or write_test_file if:
-      * Line-based editing is too complex (needs major restructuring)
-      * Multiple scattered changes across the file
-    - Then retry running tests
-13. If errors are LEGITIMATE: Call report_legitimate_failure tool with details and STOP trying to fix
-    - Provide failing test names, reason, and source code issue description
-    - The test file will be kept as-is with legitimate failing tests
-14. REQUIRED: Repeat steps 9-13 until tests pass OR legitimate failures are reported
-15. REQUIRED: Ensure all functions are tested in the test file.
-
-CRITICAL: Distinguish between test bugs (fix them) and source code bugs (report and stop)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`
-};
-// Function-wise test generation prompts
-exports.FUNCTIONWISE_PROMPTS = {
-    claude: `You are a senior software engineer tasked with writing comprehensive Jest unit tests for specific functions in a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-Test file exists: {{testFileExists}}
-Selected functions to test: {{functionNames}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-{{conditionalWarning}}
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get information about the selected functions: {{functionNames}}
-2. Use get_function_ast tool for each selected function to get detailed information
-3. Use get_imports_ast tool to understand dependencies
-4. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths
-5. Generate comprehensive Jest unit tests ONLY for these functions: {{functionNames}}
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules, models, services, and config modules
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each selected function
-   - Multiple test cases covering:
-     * Happy path scenarios
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-{{conditionalInstruction}}
-7. REQUIRED: Run the tests using run_tests tool
-8. REQUIRED: If tests fail, analyze if errors are FIXABLE or LEGITIMATE:
-   
-   FIXABLE ERRORS (fix these):
-   - Wrong import paths → use find_file + calculate_relative_path + edit tools
-   - Missing mocks → add proper jest.mock() calls
-   - Incorrect mock implementations → update mock return values
-   - Wrong test assertions → fix expect() statements
-   - TypeScript errors → fix types and imports
-   
-   LEGITIMATE FAILURES (report these):
-   - Function returns wrong type (source code bug)
-   - Missing null checks in source code
-   - Logic errors in source code
-   - Source code throws unexpected errors
-   
-9. If FIXABLE (AFTER test file is written/updated): 
-   {{conditionalFixing}}
-   - Then retry tests
-10. If LEGITIMATE: Call report_legitimate_failure with details and STOP
-11. REQUIRED: Repeat steps 7-10 until tests pass OR legitimate failures reported
-
-{{conditionalReminder}}
-
-CRITICAL: Fix test bugs but REPORT source code bugs (don't try to make broken code pass)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`,
-    openai: `You are a senior software engineer tasked with writing comprehensive Jest unit tests for specific functions in a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-Test file exists: {{testFileExists}}
-Selected functions to test: {{functionNames}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-{{conditionalWarning}}
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get information about the selected functions: {{functionNames}}
-2. Use get_function_ast tool for each selected function to get detailed information
-3. Use get_imports_ast tool to understand dependencies
-4. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths
-5. Generate comprehensive Jest unit tests ONLY for these functions: {{functionNames}}
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules, models, services, and config modules
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each selected function
-   - Multiple test cases covering:
-     * Happy path scenarios
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-{{conditionalInstruction}}
-7. REQUIRED: Run the tests using run_tests tool
-8. REQUIRED: If tests fail, analyze if errors are FIXABLE or LEGITIMATE:
-   
-   FIXABLE ERRORS (fix these):
-   - Wrong import paths → use find_file + calculate_relative_path + edit tools
-   - Missing mocks → add proper jest.mock() calls
-   - Incorrect mock implementations → update mock return values
-   - Wrong test assertions → fix expect() statements
-   - TypeScript errors → fix types and imports
-   
-   LEGITIMATE FAILURES (report these):
-   - Function returns wrong type (source code bug)
-   - Missing null checks in source code
-   - Logic errors in source code
-   - Source code throws unexpected errors
-   
-9. If FIXABLE (AFTER test file is written/updated): 
-   {{conditionalFixing}}
-   - Then retry tests
-10. If LEGITIMATE: Call report_legitimate_failure with details and STOP
-11. REQUIRED: Repeat steps 7-10 until tests pass OR legitimate failures reported
-
-{{conditionalReminder}}
-
-CRITICAL: Fix test bugs but REPORT source code bugs (don't try to make broken code pass)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`,
-    gemini: `You are a senior software engineer tasked with writing comprehensive Jest unit tests for specific functions in a TypeScript file.
-
-Source file: {{sourceFile}}
-Test file path: {{testFilePath}}
-Test file exists: {{testFileExists}}
-Selected functions to test: {{functionNames}}
-
-IMPORTANT: You MUST use the provided tools to complete this task. Do not just respond with text.
-
-{{conditionalWarning}}
-
-Your task (you MUST complete ALL steps):
-1. FIRST: Use analyze_file_ast tool to get information about the selected functions: {{functionNames}}
-2. Use get_function_ast tool for each selected function to get detailed information
-3. Use get_imports_ast tool to understand dependencies
-4. For each dependency, use find_file to locate it and calculate_relative_path to get correct import paths
-5. Generate comprehensive Jest unit tests ONLY for these functions: {{functionNames}}
-   - CRITICAL: Mock ALL imports BEFORE importing the source file to prevent initialization errors
-   - Mock database modules, models, services, and config modules
-   - Use jest.mock() calls at the TOP of the file before any imports
-   - Test suites for each selected function
-   - Multiple test cases covering:
-     * Happy path scenarios
-     * Edge cases (null, undefined, empty arrays, etc.)
-     * Error conditions
-     * Async behavior (if applicable)
-   - Proper TypeScript types
-   - Clear, descriptive test names
-   - Complete test implementations (NO placeholder comments!)
-{{conditionalInstruction}}
-7. REQUIRED: Run the tests using run_tests tool
-8. REQUIRED: If tests fail, analyze if errors are FIXABLE or LEGITIMATE:
-   
-   FIXABLE ERRORS (fix these):
-   - Wrong import paths → use find_file + calculate_relative_path + edit tools
-   - Missing mocks → add proper jest.mock() calls
-   - Incorrect mock implementations → update mock return values
-   - Wrong test assertions → fix expect() statements
-   - TypeScript errors → fix types and imports
-   
-   LEGITIMATE FAILURES (report these):
-   - Function returns wrong type (source code bug)
-   - Missing null checks in source code
-   - Logic errors in source code
-   - Source code throws unexpected errors
-   
-9. If FIXABLE (AFTER test file is written/updated): 
-   {{conditionalFixing}}
-   - Then retry tests
-10. If LEGITIMATE: Call report_legitimate_failure with details and STOP
-11. REQUIRED: Repeat steps 7-10 until tests pass OR legitimate failures reported
-
-{{conditionalReminder}}
-
-CRITICAL: Fix test bugs but REPORT source code bugs (don't try to make broken code pass)!
-
-START NOW by calling the analyze_file_ast tool with the source file path.`
-};
-//# sourceMappingURL=prompts.js.map

package/dist/prompts.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":";AAAA;;;GAGG;;;AAQH,wFAAwF;AAC3E,QAAA,gBAAgB,GAAoB;IAC/C,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EA8FgE;IAExE,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EA8FgE;IAExE,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EA8FgE;CACzE,CAAC;AAEF,wCAAwC;AAC3B,QAAA,oBAAoB,GAAoB;IACnD,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EAwDgE;IAExE,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EAwDgE;IAExE,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0EAwDgE;CACzE,CAAC"}