@autobe/agent 0.30.0-dev.20260315 → 0.30.1

package/src/orchestrate/test/histories/transformTestOperationWriteHistory.ts

@@ -1,287 +1,287 @@
-import {
-  AutoBeTestAuthorizeFunction,
-  AutoBeTestGenerateFunction,
-  AutoBeTestScenario,
-  IAutoBeCompiler,
-} from "@autobe/interface";
-import { StringUtil, transformOpenApiDocument } from "@autobe/utils";
-import { IHttpMigrateApplication } from "@typia/interface";
-import { HttpMigration } from "@typia/utils";
-import { Singleton } from "tstl";
-import typia, { OpenApi } from "typia";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
-import { getTestExternalDeclarations } from "../compile/getTestExternalDeclarations";
-import { AutoBeTestOperationProgrammer } from "../programmers/AutoBeTestOperationProgrammer";
-import { IAutoBeTestScenarioArtifacts } from "../structures/IAutoBeTestScenarioArtifacts";
-
-export async function transformTestOperationWriteHistory(
-  ctx: AutoBeContext,
-  props: {
-    instruction: string;
-    scenario: AutoBeTestScenario;
-    artifacts: IAutoBeTestScenarioArtifacts;
-    authorizationFunctions: AutoBeTestAuthorizeFunction[];
-    generationFunctions: AutoBeTestGenerateFunction[];
-  },
-): Promise<IAutoBeOrchestrateHistory> {
-  const functions: (
-    | AutoBeTestAuthorizeFunction
-    | AutoBeTestGenerateFunction
-  )[] = [...props.authorizationFunctions, ...props.generationFunctions];
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: systemPrompt.get(),
-      },
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          Here is the list of input material composition.
-
-          Make e2e test functions based on the following information.
-
-          ## Instructions
-
-          The following e2e-test-specific instructions were extracted from
-          the user's requirements and conversations. These instructions focus
-          exclusively on test-related aspects such as test data generation strategies,
-          assertion patterns, error handling approaches, and specific validation logic
-          that should be implemented in the test code.
-
-          Follow these instructions when implementing the e2e test function.
-          Carefully distinguish between:
-          - Suggestions or recommendations (consider these as guidance)
-          - Direct specifications or explicit commands (these must be followed exactly)
-
-          When instructions contain direct specifications or explicit design decisions,
-          follow them precisely even if you believe you have better alternatives.
-
-          ${props.instruction}
-
-          ## Function Name
-
-          The e2e test function name must be ${JSON.stringify(props.scenario.functionName)}.
-
-          ## Scenario Plan
-
-          Here is the scenario plan what you have to implement.
-
-          \`\`\`json
-          ${JSON.stringify(props.scenario)}
-          \`\`\`
-
-          ## DTO Definitions
-
-          You can use these DTO definitions.
-
-          Never use the DTO definitions that are not listed here.
-
-          ${await transformTestOperationWriteHistory.structures(ctx, props.artifacts)}
-
-          ## API (SDK) Functions
-
-          You can use these API functions.
-
-          Never use the functions that are not listed here.
-
-          ${transformTestOperationWriteHistory.functional(props.artifacts, functions)}
-
-          ## E2E Mockup Functions
-
-          Just reference, and never follow this code as it is.
-
-          \`\`\`json
-          ${JSON.stringify(props.artifacts.e2e)}
-          \`\`\`
-
-          ## Available Utility Functions
-
-          ${
-            functions.length > 0
-              ? StringUtil.trim`
-          🚨 **CRITICAL: UTILITY FUNCTIONS HAVE ABSOLUTE PRIORITY OVER SDK FUNCTIONS** 🚨
-
-          When calling an API endpoint, you MUST:
-          1. **FIRST**: Check if a utility function exists for that endpoint (match by METHOD + PATH)
-          2. **SECOND**: Only if NO utility function exists, use SDK function (\`api.functional.*\`)
-
-          **ABSOLUTE RULE**: If a utility function is provided for an endpoint below, you **MUST** use that utility function.
-          Using \`api.functional.*\` directly for an endpoint that has a utility function is **FORBIDDEN**.
-
-          ### Authorization Functions
-          Use these to authenticate users. They update the connection's headers internally.
-          **You MUST create a NEW connection object** with \`{ host: connection.host }\` and pass it to the authorize function.
-
-          **MANDATORY Pattern:**
-          \`\`\`typescript
-          const adminConnection: api.IConnection = { host: connection.host };
-          await authorize_admin_login(adminConnection, { body: {...} });
-          // adminConnection.headers is now updated internally by authorize function
-          // Use adminConnection for all subsequent API calls
-          \`\`\`
-
-          | Function Name | Endpoint | Actor |
-          |---------------|----------|-------|
-          ${props.authorizationFunctions
-            .map(
-              (f) =>
-                `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` | ${f.actor} |`,
-            )
-            .join("\n")}
-
-          ${props.authorizationFunctions
-            .map(
-              (f) => StringUtil.trim`
-          #### ${f.name}
-          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
-          - **Actor**: ${f.actor}
-          - **Auth Type**: ${f.authType}
-          - **Usage**: Call function, then create NEW connection with token from result
-          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
-
-          \`\`\`typescript
-          ${f.content}
-          \`\`\`
-          `,
-            )
-            .join("\n\n")}
-
-          ### Generation Functions
-          
-          Use these to create test resources. They handle data preparation and API calls internally.
-          **Pass actor-specific connection** (e.g., \`userConnection\`), NOT base \`connection\`.
-
-          | Function Name | Endpoint |
-          |---------------|----------|
-          ${props.generationFunctions
-            .map(
-              (f) =>
-                `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` |`,
-            )
-            .join("\n")}
-
-          ${props.generationFunctions
-            .map(
-              (f) => StringUtil.trim`
-          #### ${f.name}
-          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
-          - **Usage**: \`await ${f.name}(userConnection, { ... })\` - pass actor-specific connection
-          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
-
-          \`\`\`typescript
-          ${f.content}
-          \`\`\`
-          `,
-            )
-            .join("\n\n")}
-          `
-              : StringUtil.trim`
-          No utility functions are available for this test scenario.
-          You will need to handle authentication and data creation directly using the API SDK functions.
-          `
-          }
-
-          ## External Definitions
-
-          Here is the external declaration files (d.ts) you can reference.
-
-          \`\`\`json
-          ${JSON.stringify(await getTestExternalDeclarations(ctx))}
-          \`\`\`
-
-          ## Template Code
-
-          Here is the template e2e test code what you must follow.
-
-          You're only allowed to modify the "<SCENARIO DESCRIPTION HERE>" and
-          code inside the function block marked as "// <E2E TEST CODE HERE>".
-          Change the template code by writing your scenario description to the
-          comment, and filling your implementation logic into the function.
-
-          Note that, you don't need to add any "import" statement more than
-          this template code. Everything you need is already imported, so
-          make your implementation code in the import scope.
-
-          \`\`\`typescript
-          ${AutoBeTestOperationProgrammer.writeTemplateCode(props.scenario)}
-          \`\`\`
-        `,
-      },
-    ],
-    userMessage: `Write e2e test function ${props.scenario.functionName} please`,
-  };
-}
-export namespace transformTestOperationWriteHistory {
-  export async function structures(
-    ctx: AutoBeContext,
-    artifacts: IAutoBeTestScenarioArtifacts,
-  ): Promise<string> {
-    const compiler: IAutoBeCompiler = await ctx.compiler();
-    return StringUtil.trim`
-      ${Object.keys(artifacts.document.components.schemas)
-        .map((k) => `- ${k}`)
-        .join("\n")}
-
-      \`\`\`json
-      ${JSON.stringify({
-        ...artifacts.dto,
-        ...(await compiler.test.getDefaultTypes()),
-      })}
-      \`\`\`
-    `;
-  }
-
-  export function functional(
-    artifacts: IAutoBeTestScenarioArtifacts,
-    excludeFunctions: Array<
-      AutoBeTestAuthorizeFunction | AutoBeTestGenerateFunction
-    >,
-  ): string {
-    const document: OpenApi.IDocument = transformOpenApiDocument(
-      artifacts.document,
-    );
-    const app: IHttpMigrateApplication = HttpMigration.application(document);
-
-    const excludeEndpoints = new Set(
-      excludeFunctions.map(
-        (f) => `${f.endpoint.method.toLowerCase()}:${f.endpoint.path}`,
-      ),
-    );
-
-    const filteredRoutes = app.routes.filter(
-      (r) => !excludeEndpoints.has(`${r.method.toLowerCase()}:${r.path}`),
-    );
-
-    return StringUtil.trim`
-      Method | Path | Function Accessor
-      -------|------|-------------------
-      ${filteredRoutes
-        .map((r) =>
-          [r.method, r.path, `api.functional.${r.accessor.join(".")}`].join(
-            " | ",
-          ),
-        )
-        .join("\n")}
-
-      \`\`\`json
-      ${JSON.stringify(artifacts.sdk)}
-      \`\`\`
-    `;
-  }
-}
-
-const systemPrompt = new Singleton(() =>
-  AutoBeSystemPromptConstant.TEST_OPERATION_WRITE.replace(
-    "{{AutoBeTestScenario}}",
-    JSON.stringify(typia.llm.parameters<AutoBeTestScenario>()),
-  ),
-);
+import {
+  AutoBeTestAuthorizeFunction,
+  AutoBeTestGenerateFunction,
+  AutoBeTestScenario,
+  IAutoBeCompiler,
+} from "@autobe/interface";
+import { StringUtil, transformOpenApiDocument } from "@autobe/utils";
+import { IHttpMigrateApplication } from "@typia/interface";
+import { HttpMigration } from "@typia/utils";
+import { Singleton } from "tstl";
+import typia, { OpenApi } from "typia";
+import { v7 } from "uuid";
+
+import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
+import { AutoBeContext } from "../../../context/AutoBeContext";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { getTestExternalDeclarations } from "../compile/getTestExternalDeclarations";
+import { AutoBeTestOperationProgrammer } from "../programmers/AutoBeTestOperationProgrammer";
+import { IAutoBeTestScenarioArtifacts } from "../structures/IAutoBeTestScenarioArtifacts";
+
+export async function transformTestOperationWriteHistory(
+  ctx: AutoBeContext,
+  props: {
+    instruction: string;
+    scenario: AutoBeTestScenario;
+    artifacts: IAutoBeTestScenarioArtifacts;
+    authorizationFunctions: AutoBeTestAuthorizeFunction[];
+    generationFunctions: AutoBeTestGenerateFunction[];
+  },
+): Promise<IAutoBeOrchestrateHistory> {
+  const functions: (
+    | AutoBeTestAuthorizeFunction
+    | AutoBeTestGenerateFunction
+  )[] = [...props.authorizationFunctions, ...props.generationFunctions];
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: systemPrompt.get(),
+      },
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          Here is the list of input material composition.
+
+          Make e2e test functions based on the following information.
+
+          ## Instructions
+
+          The following e2e-test-specific instructions were extracted from
+          the user's requirements and conversations. These instructions focus
+          exclusively on test-related aspects such as test data generation strategies,
+          assertion patterns, error handling approaches, and specific validation logic
+          that should be implemented in the test code.
+
+          Follow these instructions when implementing the e2e test function.
+          Carefully distinguish between:
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          When instructions contain direct specifications or explicit design decisions,
+          follow them precisely even if you believe you have better alternatives.
+
+          ${props.instruction}
+
+          ## Function Name
+
+          The e2e test function name must be ${JSON.stringify(props.scenario.functionName)}.
+
+          ## Scenario Plan
+
+          Here is the scenario plan what you have to implement.
+
+          \`\`\`json
+          ${JSON.stringify(props.scenario)}
+          \`\`\`
+
+          ## DTO Definitions
+
+          You can use these DTO definitions.
+
+          Never use the DTO definitions that are not listed here.
+
+          ${await transformTestOperationWriteHistory.structures(ctx, props.artifacts)}
+
+          ## API (SDK) Functions
+
+          You can use these API functions.
+
+          Never use the functions that are not listed here.
+
+          ${transformTestOperationWriteHistory.functional(props.artifacts, functions)}
+
+          ## E2E Mockup Functions
+
+          Just reference, and never follow this code as it is.
+
+          \`\`\`json
+          ${JSON.stringify(props.artifacts.e2e)}
+          \`\`\`
+
+          ## Available Utility Functions
+
+          ${
+            functions.length > 0
+              ? StringUtil.trim`
+          🚨 **CRITICAL: UTILITY FUNCTIONS HAVE ABSOLUTE PRIORITY OVER SDK FUNCTIONS** 🚨
+
+          When calling an API endpoint, you MUST:
+          1. **FIRST**: Check if a utility function exists for that endpoint (match by METHOD + PATH)
+          2. **SECOND**: Only if NO utility function exists, use SDK function (\`api.functional.*\`)
+
+          **ABSOLUTE RULE**: If a utility function is provided for an endpoint below, you **MUST** use that utility function.
+          Using \`api.functional.*\` directly for an endpoint that has a utility function is **FORBIDDEN**.
+
+          ### Authorization Functions
+          Use these to authenticate users. They update the connection's headers internally.
+          **You MUST create a NEW connection object** with \`{ host: connection.host }\` and pass it to the authorize function.
+
+          **MANDATORY Pattern:**
+          \`\`\`typescript
+          const adminConnection: api.IConnection = { host: connection.host };
+          await authorize_admin_login(adminConnection, { body: {...} });
+          // adminConnection.headers is now updated internally by authorize function
+          // Use adminConnection for all subsequent API calls
+          \`\`\`
+
+          | Function Name | Endpoint | Actor |
+          |---------------|----------|-------|
+          ${props.authorizationFunctions
+            .map(
+              (f) =>
+                `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` | ${f.actor} |`,
+            )
+            .join("\n")}
+
+          ${props.authorizationFunctions
+            .map(
+              (f) => StringUtil.trim`
+          #### ${f.name}
+          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
+          - **Actor**: ${f.actor}
+          - **Auth Type**: ${f.authType}
+          - **Usage**: Call function, then create NEW connection with token from result
+          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
+
+          \`\`\`typescript
+          ${f.content}
+          \`\`\`
+          `,
+            )
+            .join("\n\n")}
+
+          ### Generation Functions
+          
+          Use these to create test resources. They handle data preparation and API calls internally.
+          **Pass actor-specific connection** (e.g., \`userConnection\`), NOT base \`connection\`.
+
+          | Function Name | Endpoint |
+          |---------------|----------|
+          ${props.generationFunctions
+            .map(
+              (f) =>
+                `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` |`,
+            )
+            .join("\n")}
+
+          ${props.generationFunctions
+            .map(
+              (f) => StringUtil.trim`
+          #### ${f.name}
+          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
+          - **Usage**: \`await ${f.name}(userConnection, { ... })\` - pass actor-specific connection
+          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
+
+          \`\`\`typescript
+          ${f.content}
+          \`\`\`
+          `,
+            )
+            .join("\n\n")}
+          `
+              : StringUtil.trim`
+          No utility functions are available for this test scenario.
+          You will need to handle authentication and data creation directly using the API SDK functions.
+          `
+          }
+
+          ## External Definitions
+
+          Here is the external declaration files (d.ts) you can reference.
+
+          \`\`\`json
+          ${JSON.stringify(await getTestExternalDeclarations(ctx))}
+          \`\`\`
+
+          ## Template Code
+
+          Here is the template e2e test code what you must follow.
+
+          You're only allowed to modify the "<SCENARIO DESCRIPTION HERE>" and
+          code inside the function block marked as "// <E2E TEST CODE HERE>".
+          Change the template code by writing your scenario description to the
+          comment, and filling your implementation logic into the function.
+
+          Note that, you don't need to add any "import" statement more than
+          this template code. Everything you need is already imported, so
+          make your implementation code in the import scope.
+
+          \`\`\`typescript
+          ${AutoBeTestOperationProgrammer.writeTemplateCode(props.scenario)}
+          \`\`\`
+        `,
+      },
+    ],
+    userMessage: `Write e2e test function ${props.scenario.functionName} please`,
+  };
+}
+export namespace transformTestOperationWriteHistory {
+  export async function structures(
+    ctx: AutoBeContext,
+    artifacts: IAutoBeTestScenarioArtifacts,
+  ): Promise<string> {
+    const compiler: IAutoBeCompiler = await ctx.compiler();
+    return StringUtil.trim`
+      ${Object.keys(artifacts.document.components.schemas)
+        .map((k) => `- ${k}`)
+        .join("\n")}
+
+      \`\`\`json
+      ${JSON.stringify({
+        ...artifacts.dto,
+        ...(await compiler.test.getDefaultTypes()),
+      })}
+      \`\`\`
+    `;
+  }
+
+  export function functional(
+    artifacts: IAutoBeTestScenarioArtifacts,
+    excludeFunctions: Array<
+      AutoBeTestAuthorizeFunction | AutoBeTestGenerateFunction
+    >,
+  ): string {
+    const document: OpenApi.IDocument = transformOpenApiDocument(
+      artifacts.document,
+    );
+    const app: IHttpMigrateApplication = HttpMigration.application(document);
+
+    const excludeEndpoints = new Set(
+      excludeFunctions.map(
+        (f) => `${f.endpoint.method.toLowerCase()}:${f.endpoint.path}`,
+      ),
+    );
+
+    const filteredRoutes = app.routes.filter(
+      (r) => !excludeEndpoints.has(`${r.method.toLowerCase()}:${r.path}`),
+    );
+
+    return StringUtil.trim`
+      Method | Path | Function Accessor
+      -------|------|-------------------
+      ${filteredRoutes
+        .map((r) =>
+          [r.method, r.path, `api.functional.${r.accessor.join(".")}`].join(
+            " | ",
+          ),
+        )
+        .join("\n")}
+
+      \`\`\`json
+      ${JSON.stringify(artifacts.sdk)}
+      \`\`\`
+    `;
+  }
+}
+
+const systemPrompt = new Singleton(() =>
+  AutoBeSystemPromptConstant.TEST_OPERATION_WRITE.replace(
+    "{{AutoBeTestScenario}}",
+    JSON.stringify(typia.llm.parameters<AutoBeTestScenario>()),
+  ),
+);