@autobe/agent 0.28.0 → 0.29.0

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

@@ -1,125 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeInterfaceAuthorization, AutoBeOpenApi } from "@autobe/interface";
-import { MapUtil, StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { IAutoBeTestScenarioAuthorizationActor } from "../structures/IAutoBeTestScenarioAuthorizationActor";
-import { getPrerequisites } from "../utils/getPrerequisites";
-
-export const transformTestScenarioHistories = (props: {
-  state: AutoBeState;
-  document: AutoBeOpenApi.IDocument;
-  include: AutoBeOpenApi.IOperation[];
-  exclude: Pick<AutoBeOpenApi.IOperation, "method" | "path">[];
-  instruction: string;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  const authorizations: AutoBeInterfaceAuthorization[] =
-    props.state.interface?.authorizations ?? [];
-  const authorizationActors: Map<
-    string,
-    IAutoBeTestScenarioAuthorizationActor
-  > = new Map();
-
-  for (const authorization of authorizations) {
-    for (const op of authorization.operations) {
-      if (op.authorizationType === null) continue;
-      const value: IAutoBeTestScenarioAuthorizationActor = MapUtil.take(
-        authorizationActors,
-        authorization.name,
-        () => ({
-          name: authorization.name,
-          join: null,
-          login: null,
-        }),
-      );
-      if (op.authorizationType === "join") value.join = op;
-      else if (op.authorizationType === "login") value.login = op;
-    }
-  }
-
-  return [
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: AutoBeSystemPromptConstant.TEST_SCENARIO,
-    } satisfies IAgenticaHistoryJson.ISystemMessage,
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "assistantMessage",
-      text: StringUtil.trim`
-        ## 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 coverage priorities,
-        specific edge cases to validate, business logic verification strategies,
-        and critical user workflows that must be tested.
-        
-        Follow these instructions when generating test scenarios.
-        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}
-
-        ## API Operations
-
-        Below are the complete API operations.
-        Use this information to understand capabilities and dependency relationships.
-        Generate scenarios only for endpoints listed in "Included in Test Plan".
-        Other operations may be referenced as dependencies only.
-
-        You may write multiple scenarios for a single included endpoint.
-        Focus on business-logic-oriented E2E flows rather than trivial CRUD.
-
-        \`\`\`json
-        ${JSON.stringify({
-          operations: props.document.operations,
-        })}
-        \`\`\`
-
-        ## Included in Test Plan
-
-        Below are the endpoints that have been included in the test plan.
-        Each endpoint shows its authentication requirements and related authentication APIs.
-        When testing endpoints that require authentication, ensure you include the corresponding 
-        join/login operations in your test scenario to establish proper authentication context.
-
-        \`\`\`json
-        ${JSON.stringify(
-          props.include.map((el) => ({
-            ...el,
-            prerequisites: getPrerequisites({
-              document: props.document,
-              endpoint: el,
-            }),
-            authorizationActors: Array.from(
-              authorizationActors.values(),
-            ).filter((actor) => actor.name === el.authorizationActor),
-          })),
-        )}
-        \`\`\`
-
-        ## Excluded from Test Plan
-
-        These are the endpoints that have already been used in test codes generated as part of a plan group.
-        These endpoints do not need to be tested again.
-        However, it is allowed to reference or depend on these endpoints when writing test codes for other purposes.
-
-        \`\`\`json
-        ${JSON.stringify(props.exclude)}
-        \`\`\`
-
-      `,
-    } satisfies IAgenticaHistoryJson.IAssistantMessage,
-  ];
-};

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

@@ -1,89 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { IAutoBeTestScenarioApplication } from "../structures/IAutoBeTestScenarioApplication";
-import { getPrerequisites } from "../utils/getPrerequisites";
-
-export function transformTestScenarioReviewHistories(props: {
-  state: AutoBeState;
-  instruction: string;
-  groups: IAutoBeTestScenarioApplication.IScenarioGroup[];
-}): Array<
-  IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage
-> {
-  const document: AutoBeOpenApi.IDocument | undefined =
-    props.state.interface?.document;
-  if (document === undefined) {
-    throw new Error(
-      "Cannot review test scenarios because there are no operations.",
-    );
-  }
-
-  return [
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: AutoBeSystemPromptConstant.TEST_SCENARIO,
-    },
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: AutoBeSystemPromptConstant.TEST_SCENARIO_REVIEW,
-    },
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "assistantMessage",
-      text: StringUtil.trim`
-        ## 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 coverage priorities,
-        specific edge cases to validate, business logic verification strategies,
-        and critical user workflows that must be tested.
-        
-        Follow these instructions when reviewing test scenarios.
-        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}
-
-        ## Available API Operations for Reference
-
-        Below are all available API operations and interface schemas for validation purposes.
-        Match each operation with its corresponding schema.
-
-        \`\`\`json
-        ${JSON.stringify({ operations: document.operations })}
-        \`\`\`
-
-        ## Test Scenario Groups to Review
-
-        Each scenario group includes the target endpoint and its prerequisite endpoints.
-
-        \`\`\`json
-        ${JSON.stringify(
-          props.groups.map((g) => ({
-            ...g,
-            prerequisites: getPrerequisites({
-              document,
-              endpoint: g.endpoint,
-            }),
-          })),
-        )}
-        \`\`\`
-      `,
-    },
-  ];
-}

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

@@ -1,172 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeTestScenario } from "@autobe/interface";
-import { StringUtil, transformOpenApiDocument } from "@autobe/utils";
-import {
-  HttpMigration,
-  IHttpMigrateApplication,
-  ILlmSchema,
-  OpenApi,
-} from "@samchon/openapi";
-import { Singleton } from "tstl";
-import typia from "typia";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-import { getTestExternalDeclarations } from "../compile/getTestExternalDeclarations";
-import { IAutoBeTestScenarioArtifacts } from "../structures/IAutoBeTestScenarioArtifacts";
-
-export async function transformTestWriteHistories<
-  Model extends ILlmSchema.Model,
->(
-  ctx: AutoBeContext<Model>,
-  props: {
-    instruction: string;
-    scenario: AutoBeTestScenario;
-    artifacts: IAutoBeTestScenarioArtifacts;
-  },
-): Promise<
-  Array<
-    IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage
-  >
-> {
-  return [
-    {
-      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.
-
-        ${transformTestWriteHistories.structures(props.artifacts)}
-
-        ## API (SDK) Functions
-
-        You can use these API functions.
-
-        Never use the functions that are not listed here.
-
-        ${transformTestWriteHistories.functional(props.artifacts)}
-
-        ## E2E Mockup Functions
-
-        Just reference, and never follow this code as it is.
-
-        \`\`\`json
-        ${JSON.stringify(props.artifacts.e2e)}
-        \`\`\`
-
-        ## 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
-        ${props.artifacts.template}
-        \`\`\`
-      `,
-    },
-  ];
-}
-export namespace transformTestWriteHistories {
-  export function structures(artifacts: IAutoBeTestScenarioArtifacts): string {
-    return StringUtil.trim`
-      ${Object.keys(artifacts.document.components.schemas)
-        .map((k) => `- ${k}`)
-        .join("\n")}
-
-      \`\`\`json
-      ${JSON.stringify(artifacts.dto)}
-      \`\`\`
-    `;
-  }
-
-  export function functional(artifacts: IAutoBeTestScenarioArtifacts): string {
-    const document: OpenApi.IDocument = transformOpenApiDocument(
-      artifacts.document,
-    );
-    const app: IHttpMigrateApplication = HttpMigration.application(document);
-    return StringUtil.trim`
-      Method | Path | Function Accessor
-      -------|------|-------------------
-      ${app.routes
-        .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_WRITE.replace(
-    "{{AutoBeTestScenario}}",
-    JSON.stringify(typia.llm.parameters<AutoBeTestScenario, "claude">()),
-  ),
-);