@autobe/agent 0.20.0 → 0.22.0

package/src/orchestrate/test/orchestrateTestWrite.ts

@@ -50,7 +50,7 @@ export async function orchestrateTestWrite<Model extends ILlmSchema.Model>(
           artifacts,
           event,
         };
-      } catch {
+      } catch (error) {
         return null;
       }
     }),
@@ -73,7 +73,7 @@ async function process<Model extends ILlmSchema.Model>(
   };
   const { tokenUsage } = await ctx.conversate({
     source: "testWrite",
-    histories: transformTestWriteHistories(scenario, artifacts),
+    histories: await transformTestWriteHistories(ctx, scenario, artifacts),
     controller: createController({
       model: ctx.model,
       artifacts,
@@ -85,16 +85,30 @@ async function process<Model extends ILlmSchema.Model>(
     promptCacheKey,
     message: "Create e2e test functions.",
   });
-  if (pointer.value === null) throw new Error("Failed to create test code.");
+  if (pointer.value === null) {
+    ++progress.completed;
+    throw new Error("Failed to create test code.");
+  }
 
   const compiler: IAutoBeCompiler = await ctx.compiler();
-  pointer.value.final = await compiler.typescript.beautify(pointer.value.final);
+  if (pointer.value.revise)
+    pointer.value.revise.final = await compiler.typescript.beautify(
+      pointer.value.revise.final,
+    );
+  else
+    pointer.value.draft = await compiler.typescript.beautify(
+      pointer.value.draft,
+    );
   return {
     type: "testWrite",
     id: v7(),
     created_at: new Date().toISOString(),
     location: `test/features/api/${pointer.value.domain}/${scenario.functionName}.ts`,
-    ...pointer.value,
+    scenario: pointer.value.scenario,
+    domain: pointer.value.domain,
+    draft: pointer.value.draft,
+    review: pointer.value.revise?.review,
+    final: pointer.value.revise?.final,
     tokenUsage,
     completed: ++progress.completed,
     total: progress.total,
@@ -119,7 +133,11 @@ function createController<Model extends ILlmSchema.Model>(props: {
     execute: {
       write: (next) => {
         next.draft = completeTestCode(props.artifacts, next.draft);
-        next.final = completeTestCode(props.artifacts, next.final);
+        if (next.revise)
+          next.revise.final = completeTestCode(
+            props.artifacts,
+            next.revise.final,
+          );
         props.build(next);
       },
     } satisfies IAutoBeTestWriteApplication,

package/src/orchestrate/test/structures/IAutoBeTestCorrectApplication.ts

@@ -4,16 +4,14 @@ export interface IAutoBeTestCorrectApplication {
    * generates corrected E2E test code.
    *
    * The AI executes this function to perform the complete error correction
-   * workflow: error-free analysis → compilation error analysis → draft
-   * correction → code review → final corrected implementation. This multi-step
-   * process ensures systematic error resolution while preserving original test
-   * functionality and maintaining code quality.
+   * workflow: compilation error analysis → draft correction → code review →
+   * final corrected implementation. This multi-step process ensures systematic
+   * error resolution while preserving original test functionality and
+   * maintaining code quality.
    *
-   * The corrector first analyzes the scenario without considering compilation
-   * errors to understand the intended functionality, then incorporates
-   * compilation diagnostics to identify specific issues, and finally produces
-   * corrected code through iterative refinement with comprehensive review and
-   * validation.
+   * The corrector analyzes compilation diagnostics to identify specific issues,
+   * develops correction strategies, and produces corrected code through
+   * iterative refinement with comprehensive review and validation.
    *
    * @param props Complete specification for error correction workflow including
    *   analysis steps, draft implementation, review process, and final code
@@ -25,47 +23,30 @@ export interface IAutoBeTestCorrectApplication {
 export namespace IAutoBeTestCorrectApplication {
   export interface IProps {
     /**
-     * Step 1: Initial analysis and understanding without compilation error
-     * context.
-     *
-     * AI analyzes the original test scenario, business requirements, and
-     * intended functionality without being influenced by compilation errors.
-     * This clean analysis establishes a clear understanding of what the test
-     * accomplishes, the expected business workflow, and the correct API
-     * integration patterns.
-     *
-     * This step ensures that error correction doesn't lose sight of the
-     * original test purpose and helps maintain the intended business logic
-     * while addressing technical compilation issues. The AI develops a
-     * comprehensive understanding of the test requirements before diving into
-     * error-specific details.
-     *
-     * Workflow: Scenario understanding → Business logic analysis → Intended
-     * functionality mapping
-     */
-    think_without_compile_error: string;
-
-    /**
-     * Step 2: Compilation error analysis and root cause identification.
+     * Step 1: Deep compilation error analysis and correction strategy.
+     *
+     * AI performs comprehensive analysis of compilation errors to develop
+     * targeted correction strategies. This step involves deep examination of
+     * error messages, identification of error patterns, understanding root
+     * causes, and planning systematic corrections.
      *
-     * AI re-analyzes the scenario and implementation with full awareness of
-     * compilation errors and diagnostic information. This step involves
-     * systematic examination of error messages, identification of error
-     * patterns, and understanding of how compilation issues relate to the
-     * intended functionality.
+     * The AI examines each compilation diagnostic to understand where the
+     * implementation diverged from correct TypeScript usage, identifies the
+     * business logic intent behind the failed code, and formulates strategies
+     * to fix errors while preserving the original test purpose. This analysis
+     * correlates error patterns with code structure to ensure corrections
+     * address root causes rather than symptoms.
      *
-     * The AI correlates compilation diagnostics with the original requirements
-     * to understand where the implementation diverged from correct TypeScript
-     * usage while maintaining the business logic intent. This analysis forms
-     * the foundation for targeted error correction strategies.
+     * This deep analysis forms the foundation for all subsequent correction
+     * efforts, ensuring a methodical approach to resolving compilation issues.
      *
      * Workflow: Error diagnostic analysis → Root cause identification →
-     * Correction strategy planning
+     * Correction strategy planning → Business logic preservation strategy
      */
-    think_again_with_compile_error: string;
+    think: string;
 
     /**
-     * Step 3: Draft corrected TypeScript E2E test code implementation.
+     * Step 2: Draft corrected TypeScript E2E test code implementation.
      *
      * AI generates the first corrected version of the test code based on error
      * analysis and correction strategies. This draft addresses all identified
@@ -86,7 +67,29 @@ export namespace IAutoBeTestCorrectApplication {
     draft: string;
 
     /**
-     * Step 4: Code review and correction validation.
+     * Step 3-4: Review and finalization process.
+     *
+     * Encapsulates the review and final implementation phases into a single
+     * revision process. This structured approach ensures systematic validation
+     * and refinement of the corrected code through comprehensive review
+     * followed by production-ready implementation.
+     *
+     * The revision process maintains clear separation between review feedback
+     * and final deliverable while ensuring all corrections are properly
+     * validated and integrated.
+     */
+    revise: IReviseProps;
+  }
+
+  /**
+   * Revision properties for the final review and implementation phases.
+   *
+   * This interface encapsulates the final two steps of the error correction
+   * workflow, ensuring systematic review and production-ready code delivery.
+   */
+  export interface IReviseProps {
+    /**
+     * Step 3: Code review and correction validation.
      *
      * AI performs a comprehensive review of the corrected draft implementation,
      * validating that all compilation errors have been resolved and that the
@@ -105,7 +108,7 @@ export namespace IAutoBeTestCorrectApplication {
     review: string;
 
     /**
-     * Step 5: Final production-ready corrected test code.
+     * Step 4: Final production-ready corrected test code.
      *
      * AI produces the final, polished version of the corrected test code
      * incorporating all review feedback and validation results. This code
@@ -119,7 +122,7 @@ export namespace IAutoBeTestCorrectApplication {
      * behaviors and user workflows.
      *
      * Workflow: Review integration → Final refinement → Production-ready
-     * implementation This is the ultimate deliverable that will replace the
+     * implementation. This is the ultimate deliverable that will replace the
      * compilation-failed code.
      */
     final: string;

package/src/orchestrate/test/structures/IAutoBeTestFunctionFailure.ts

@@ -0,0 +1,8 @@
+import { IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+
+import { IAutoBeTestFunction } from "./IAutoBeTestFunction";
+
+export interface IAutoBeTestFunctionFailure {
+  function: IAutoBeTestFunction;
+  failure: IAutoBeTypeScriptCompileResult.IFailure;
+}

package/src/orchestrate/test/structures/IAutoBeTestScenarioApplication.ts

@@ -32,6 +32,18 @@ export namespace IAutoBeTestScenarioApplication {
      *
      * Each scenario represents a specific test case for the same `path` and
      * `method`.
+     *
+     * IMPORTANT: Each scenario must be actually implementable. A scenario's
+     * implementability is determined by the existence of ALL APIs (endpoints)
+     * required to test it. This includes not only the primary endpoint being
+     * tested, but also ALL dependency endpoints needed for setup,
+     * authentication, and data preparation. If even one required dependency API
+     * is missing from the available operations, the scenario cannot be
+     * implemented and should not be generated.
+     *
+     * Example: A "test banned user login" scenario requires both a login API
+     * AND a ban user API. If the ban API doesn't exist, this scenario is not
+     * implementable regardless of database schema fields.
      */
     scenarios: IScenario[] & tags.MinItems<1>;
   }
@@ -42,6 +54,11 @@ export namespace IAutoBeTestScenarioApplication {
    * This interface defines a structured, user-centric test draft that includes
    * a descriptive function name, a detailed scenario draft, and logical
    * dependencies on other endpoints required for context or setup.
+   *
+   * CRITICAL: All referenced endpoints MUST exist in the provided API
+   * operations. Do NOT create scenarios for non-existent APIs, even if database
+   * schema fields suggest their existence. Test scenarios must be implementable
+   * with available APIs only.
    */
   export interface IScenario {
     /**
@@ -120,12 +137,22 @@ export namespace IAutoBeTestScenarioApplication {
      * authentication, resource creation, or data setup, that are relevant to
      * the test. This list is not a strict execution order — if ordering is
      * important, it must be described explicitly in the `purpose`.
+     *
+     * WARNING: Every endpoint referenced here MUST exist in the provided API
+     * operations. Do NOT reference endpoints that are not explicitly available,
+     * even if they seem logically necessary based on database schema or
+     * business logic.
      */
     dependencies: IDependencies[];
   }
 
   export interface IDependencies {
-    /** Target API endpoint that this scenario depends on. */
+    /**
+     * Target API endpoint that this scenario depends on.
+     *
+     * This endpoint MUST exist in the available API operations list.
+     * Non-existent endpoints will cause test implementation failures.
+     */
     endpoint: AutoBeOpenApi.IEndpoint;
 
     /**

package/src/orchestrate/test/structures/IAutoBeTestScenarioArtifacts.ts

@@ -5,4 +5,5 @@ export interface IAutoBeTestScenarioArtifacts {
   sdk: Record<string, string>;
   dto: Record<string, string>;
   e2e: Record<string, string>;
+  template: string;
 }

package/src/orchestrate/test/structures/IAutoBeTestWriteApplication.ts

@@ -60,6 +60,20 @@ export namespace IAutoBeTestWriteApplication {
      */
     draft: string;
 
+    /**
+     * Steps 4-5: Code review and final refinement process.
+     *
+     * Contains the iterative improvement workflow that transforms the initial
+     * draft into production-ready test code. This two-phase process ensures
+     * systematic quality enhancement through comprehensive review followed by
+     * targeted refinement based on identified issues.
+     *
+     * Workflow: Draft → Review analysis → Final implementation
+     */
+    revise: IReviseProps;
+  }
+
+  export interface IReviseProps {
     /**
      * Step 4: Code review and quality assessment.
      *

package/src/orchestrate/test/utils/getReferenceIds.ts

@@ -0,0 +1,25 @@
+import { AutoBeOpenApi } from "@autobe/interface";
+import { OpenApiTypeChecker } from "@samchon/openapi";
+
+export const getReferenceIds = (props: {
+  document: AutoBeOpenApi.IDocument;
+  operation: AutoBeOpenApi.IOperation;
+}): string[] => {
+  const result: Set<string> = new Set();
+  const emplace = (key: string) => {
+    if (key.endsWith("_id")) result.add(key);
+  };
+
+  props.operation.parameters.forEach((p) => emplace(p.name));
+  if (props.operation.requestBody) {
+    OpenApiTypeChecker.visit({
+      components: props.document.components,
+      schema: { $ref: props.operation.requestBody.typeName },
+      closure: (schema) => {
+        if (OpenApiTypeChecker.isObject(schema) === false) return;
+        for (const key of Object.keys(schema.properties ?? {})) emplace(key);
+      },
+    });
+  }
+  return Array.from(result);
+};

package/src/structures/IAutoBeConfig.ts

@@ -16,6 +16,9 @@
  * @author Samchon
  */
 export interface IAutoBeConfig {
+  /** @default 4 */
+  retry?: number;
+
   /**
    * Language and cultural locale preference for AI agent communication.
    *

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.d.ts

@@ -1,38 +0,0 @@
-import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
-export declare namespace IAutoBeRealizeScenarioApplication {
-    interface IProps {
-        /** The OpenAPI operation to be realized. */
-        operation: AutoBeOpenApi.IOperation;
-        /**
-         * The name of the function to be generated.
-         *
-         * Derived from the Swagger path and method. The function name must be
-         * written in snake_case. It serves as the entry point in both code
-         * generation and test code.
-         *
-         * Once the function is generated, the function name and file name will be
-         * the same. The generated file will be located at
-         * `src/providers/${function_name}.ts`.
-         */
-        functionName: string;
-        /** For example, `src/providers/${function_name}.ts`. */
-        location: string;
-        /**
-         * List of scenario descriptions for test code generation.
-         *
-         * Each scenario describes the expected behavior of the function under
-         * certain conditions. Used as a basis for TDD-style automated test
-         * generation.
-         */
-        testScenarios: string[];
-        /**
-         * Optional decorator event for customizing code generation behavior.
-         *
-         * Provides additional metadata or instructions that can modify how the
-         * function implementation is generated. Can include custom annotations,
-         * middleware configurations, or special handling directives that affect the
-         * final code output.
-         */
-        decoratorEvent?: AutoBeRealizeAuthorization;
-    }
-}

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"IAutoBeRealizeScenarioApplication.js","sourceRoot":"","sources":["../../../../../../src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.ts"],"names":[],"mappings":""}

package/lib/agent/src/orchestrate/test/histories/transformTestHistories.d.ts

@@ -1,3 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeState } from "../../../context/AutoBeState";
-export declare const transformTestHistories: (state: AutoBeState) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/agent/src/orchestrate/test/histories/transformTestHistories.js

@@ -1,75 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.transformTestHistories = void 0;
-const utils_1 = require("@autobe/utils");
-const uuid_1 = require("uuid");
-const transformTestHistories = (state) => {
-    if (state.analyze === null)
-        return [
-            {
-                id: (0, uuid_1.v7)(),
-                created_at: new Date().toISOString(),
-                type: "systemMessage",
-                text: utils_1.StringUtil.trim `
-          Requirement analysis is not yet completed.
-          Don't call the any tool function,
-          but say to process the requirement analysis.
-        `,
-            },
-        ];
-    else if (state.prisma === null)
-        return [
-            {
-                id: (0, uuid_1.v7)(),
-                created_at: new Date().toISOString(),
-                type: "systemMessage",
-                text: utils_1.StringUtil.trim `
-          Prisma DB schema generation is not yet completed.
-          Don't call the any tool function,
-          but say to process the Prisma DB schema generation.
-        `,
-            },
-        ];
-    else if (state.analyze.step !== state.prisma.step)
-        return [
-            {
-                id: (0, uuid_1.v7)(),
-                created_at: new Date().toISOString(),
-                type: "systemMessage",
-                text: utils_1.StringUtil.trim `
-          Prisma DB schema generation has not been updated
-          for the latest requirement analysis.
-          Don't call the any tool function,
-          but say to re-process the Prisma DB schema generation.
-        `,
-            },
-        ];
-    else if (state.prisma.compiled.type !== "success")
-        return [
-            {
-                id: (0, uuid_1.v7)(),
-                created_at: new Date().toISOString(),
-                type: "systemMessage",
-                text: utils_1.StringUtil.trim `
-          Prisma DB schema generation has not been updated
-          for the latest requirement analysis.
-          Don't call the any tool function,
-          but say to re-process the Prisma DB schema generation.
-        `,
-            },
-        ];
-    return [
-        {
-            id: (0, uuid_1.v7)(),
-            created_at: new Date().toISOString(),
-            type: "systemMessage",
-            text: utils_1.StringUtil.trim `
-        Interface generation is not yet completed.
-        Don't call the any tool function,
-        but say to process the interface generation.
-      `,
-        },
-    ];
-};
-exports.transformTestHistories = transformTestHistories;
-//# sourceMappingURL=transformTestHistories.js.map

package/lib/agent/src/orchestrate/test/histories/transformTestHistories.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformTestHistories.js","sourceRoot":"","sources":["../../../../../../src/orchestrate/test/histories/transformTestHistories.ts"],"names":[],"mappings":";;;AACA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,sBAAsB,GAAG,CACpC,KAAkB,EAGlB,EAAE;IACF,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI;QACxB,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;SAIpB;aACF;SACF,CAAC;SACC,IAAI,KAAK,CAAC,MAAM,KAAK,IAAI;QAC5B,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;SAIpB;aACF;SACF,CAAC;SACC,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,KAAK,CAAC,MAAM,CAAC,IAAI;QAC/C,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;SAKpB;aACF;SACF,CAAC;SACC,IAAI,KAAK,CAAC,MAAM,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS;QAC/C,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;SAKpB;aACF;SACF,CAAC;IACJ,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;OAIpB;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AAvEW,QAAA,sBAAsB,0BAuEjC"}

package/lib/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.d.ts

@@ -1,38 +0,0 @@
-import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
-export declare namespace IAutoBeRealizeScenarioApplication {
-    interface IProps {
-        /** The OpenAPI operation to be realized. */
-        operation: AutoBeOpenApi.IOperation;
-        /**
-         * The name of the function to be generated.
-         *
-         * Derived from the Swagger path and method. The function name must be
-         * written in snake_case. It serves as the entry point in both code
-         * generation and test code.
-         *
-         * Once the function is generated, the function name and file name will be
-         * the same. The generated file will be located at
-         * `src/providers/${function_name}.ts`.
-         */
-        functionName: string;
-        /** For example, `src/providers/${function_name}.ts`. */
-        location: string;
-        /**
-         * List of scenario descriptions for test code generation.
-         *
-         * Each scenario describes the expected behavior of the function under
-         * certain conditions. Used as a basis for TDD-style automated test
-         * generation.
-         */
-        testScenarios: string[];
-        /**
-         * Optional decorator event for customizing code generation behavior.
-         *
-         * Provides additional metadata or instructions that can modify how the
-         * function implementation is generated. Can include custom annotations,
-         * middleware configurations, or special handling directives that affect the
-         * final code output.
-         */
-        decoratorEvent?: AutoBeRealizeAuthorization;
-    }
-}

package/lib/orchestrate/test/histories/transformTestHistories.d.ts

@@ -1,3 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeState } from "../../../context/AutoBeState";
-export declare const transformTestHistories: (state: AutoBeState) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

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

@@ -1,78 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeState } from "../../../context/AutoBeState";
-
-export const transformTestHistories = (
-  state: AutoBeState,
-): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  if (state.analyze === null)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: StringUtil.trim`
-          Requirement analysis is not yet completed.
-          Don't call the any tool function,
-          but say to process the requirement analysis.
-        `,
-      },
-    ];
-  else if (state.prisma === null)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: StringUtil.trim`
-          Prisma DB schema generation is not yet completed.
-          Don't call the any tool function,
-          but say to process the Prisma DB schema generation.
-        `,
-      },
-    ];
-  else if (state.analyze.step !== state.prisma.step)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: StringUtil.trim`
-          Prisma DB schema generation has not been updated
-          for the latest requirement analysis.
-          Don't call the any tool function,
-          but say to re-process the Prisma DB schema generation.
-        `,
-      },
-    ];
-  else if (state.prisma.compiled.type !== "success")
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: StringUtil.trim`
-          Prisma DB schema generation has not been updated
-          for the latest requirement analysis.
-          Don't call the any tool function,
-          but say to re-process the Prisma DB schema generation.
-        `,
-      },
-    ];
-  return [
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: StringUtil.trim`
-        Interface generation is not yet completed.
-        Don't call the any tool function,
-        but say to process the interface generation.
-      `,
-    },
-  ];
-};