Add test data

Author: yasithrashan

workspaces/ballerina/ballerina-extension/src/features/ai/agent/tools/text-editor.ts

@@ -895,9 +895,8 @@ export function createReadTool(execute: ReadExecute) {
     - You can optionally specify a line offset and limit (especially handy for long files).
     - Any lines longer than 2000 characters will be truncated
     - The file content will be returned as string
-    - By default, it reads up to lines starting from the beginning of the file
-    - You can optionally specify a line offset and limit (especially handy for long files)
-    - For read a specific **component** of a file, If you know the line range ALWAYS prefer read that specific line range rather than the entire file.
+    - If you know the exact line range of a COMPONENT you want to read, ALWAYS prefer reading that specific line range rather than the entire file.
+    - If you dont know the line range to read, start by reading the entire file.
     - If the file is very large, consider using the offset and limit parameters to read it in chunks.
     - If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.`,
     inputSchema: z.object({

workspaces/ballerina/ballerina-extension/test/ai/evals/code/result-management/result-persistence.ts

@@ -91,6 +91,7 @@ export async function persistUsecaseResult(
 
     for (const file of usecaseResult.files) {
         const filePath = path.join(codeDir, file.fileName);
+        await fs.promises.mkdir(path.dirname(filePath), { recursive: true });
         await fs.promises.writeFile(filePath, file.content);
     }
 

workspaces/ballerina/ballerina-extension/test/ai/evals/code/test-cases.ts

@@ -194,10 +194,10 @@ export const textEditSpecializedTestCases = [
 ];
 
 export const testCasesForExistingProject = [
-  {
-    prompt: "How can I implement distributed tracing with OpenTelemetry across the order service saga, ensuring that trace contexts are properly propagated through Kafka events and database transactions while maintaining correlation IDs for debugging payment and fulfillment failures?",
-    projectPath: "simple_order_management_system"
-  },
+  // {
+  //   prompt: "How can I implement distributed tracing with OpenTelemetry across the order service saga, ensuring that trace contexts are properly propagated through Kafka events and database transactions while maintaining correlation IDs for debugging payment and fulfillment failures?",
+  //   projectPath: "simple_order_management_system"
+  // },
   // {
   //   prompt: "I need to refactor the current synchronous order creation flow to support asynchronous batch processing with dead letter queues for failed orders, implementing circuit breaker patterns for the pricing service calls and adding retry mechanisms with exponential backoff for Kafka publishing failures.",
   //   projectPath: "simple_order_management_system"
@@ -366,8 +366,20 @@ export const langlibTestCases = [
 ];
 
 export const testCasesForCodeIndexing = [
+  // {
+  //   prompt: "Refactor the customer creation flow to persist newly created customers in a SQL database instead of the in-memory customerStore map, implementing a repository layer with connection pooling, parameterized queries for security, and proper error handling for database failures while maintaining data validation and response consistency in the CustomerService.",
+  //   projectPath: "order_management_system"
+  // },
+  {
+    prompt: "Change the delete endpoint in CustomerService so that instead of permanently removing the customer, it marks them as inactive by setting a deletedAt timestamp.",
+    projectPath: "order_management_system"
+  },
+  {
+    prompt: "Add a stockQuantity validation to the order creation flow so that when an order is successfully placed, the stock count of each ordered product is decremented in the product store.",
+    projectPath: "order_management_system"
+  },
   {
-    prompt: "Refactor the customer creation flow to persist newly created customers in a SQL database instead of the in-memory customerStore map, implementing a repository layer with connection pooling, parameterized queries for security, and proper error handling for database failures while maintaining data validation and response consistency in the CustomerService.",
+    prompt: "Add a coupon code system where customers can apply a discount coupon during order creation. The coupon should validate against a coupon store and reduce the total order amount accordingly.",
     projectPath: "order_management_system"
   }
 ];
@@ -379,3 +391,4 @@ testCases.push(...textEditSpecializedTestCases);
 testCases.push(...testCasesForExistingProject);
 testCases.push(...testCasesForExistingSemanticErrors);
 testCases.push(...langlibTestCases);
+testCases.push(...testCasesForCodeIndexing);

workspaces/ballerina/ballerina-extension/test/data/order_management_system/Ballerina.toml

@@ -0,0 +1,8 @@
+[package]
+org = "test"
+name = "order_management_system"
+version = "0.1.0"
+distribution = "2201.13.1"
+
+[build-options]
+observabilityIncluded = true