@autobe/agent 0.7.3 → 0.9.0

package/lib/orchestrate/test/orchestrateTestScenario.js

@@ -49,105 +49,281 @@ exports.orchestrateTestScenario = orchestrateTestScenario;
 const __typia_transform__validateReport = __importStar(require("typia/lib/internal/_validateReport.js"));
 const core_1 = require("@agentica/core");
 const typia_1 = __importDefault(require("typia"));
+const uuid_1 = require("uuid");
 const assertSchemaModel_1 = require("../../context/assertSchemaModel");
-const transformTestScenarioHistories_1 = require("./transformTestScenarioHistories");
+const divideArray_1 = require("../../utils/divideArray");
+const enforceToolCall_1 = require("../../utils/enforceToolCall");
 function orchestrateTestScenario(ctx) {
     return __awaiter(this, void 0, void 0, function* () {
-        var _a, _b, _c, _d, _e, _f;
-        const files = Object.entries((_b = (_a = ctx.state().interface) === null || _a === void 0 ? void 0 : _a.files) !== null && _b !== void 0 ? _b : {})
-            .filter(([filename]) => {
-            return filename.startsWith("test/features/api/");
-        })
-            .reduce((acc, [filename, content]) => {
-            return Object.assign(acc, { [filename]: content });
-        }, {});
-        const operations = (_d = (_c = ctx.state().interface) === null || _c === void 0 ? void 0 : _c.document.operations) !== null && _d !== void 0 ? _d : [];
-        const endpoints = operations.map((it) => {
-            return {
-                method: it.method,
-                path: it.path,
-                summary: it.summary,
-                description: it.description,
-                parameters: it.parameters,
-                requestBody: it.requestBody,
-                responseBody: it.responseBody,
-            };
-        });
-        const start = new Date();
-        let completed = 0;
-        const scenarios = yield Promise.all(endpoints.map((endpoint, i, arr) => __awaiter(this, void 0, void 0, function* () {
-            var _a, _b;
-            const endponits = arr.filter((_el, j) => i !== j);
-            const rows = yield process(ctx, endpoint, endponits, files);
-            ctx.dispatch({
-                type: "testScenario",
-                scenarios: rows,
-                total: rows.flatMap((el) => el.scenarios).length,
-                step: (_b = (_a = ctx.state().test) === null || _a === void 0 ? void 0 : _a.step) !== null && _b !== void 0 ? _b : 0,
-                completed,
-                created_at: start.toISOString(),
+        var _a, _b, _c, _d;
+        const operations = (_b = (_a = ctx.state().interface) === null || _a === void 0 ? void 0 : _a.document.operations) !== null && _b !== void 0 ? _b : [];
+        if (operations.length === 0) {
+            throw new Error("Cannot write test scenarios because these are no operations.");
+        }
+        const exclude = [];
+        let include = Array.from(operations);
+        do {
+            const matrix = (0, divideArray_1.divideArray)({ array: include, capacity: 30 });
+            yield Promise.all(matrix.map((_include) => __awaiter(this, void 0, void 0, function* () {
+                exclude.push(...(yield execute(ctx, operations, _include, exclude.map((x) => x.endpoint))));
+            })));
+            include = include.filter((op) => {
+                if (exclude.some((pg) => pg.endpoint.method === op.method && pg.endpoint.path === op.path)) {
+                    return false;
+                }
+                return true;
             });
-            return rows;
-        })));
+        } while (include.length > 0);
         return {
             type: "testScenario",
-            scenarios: scenarios.flat(),
-            total: scenarios.flat().flatMap((el) => el.scenarios).length,
-            step: (_f = (_e = ctx.state().test) === null || _e === void 0 ? void 0 : _e.step) !== null && _f !== void 0 ? _f : 0,
-            completed,
-            created_at: start.toISOString(),
+            step: (_d = (_c = ctx.state().analyze) === null || _c === void 0 ? void 0 : _c.step) !== null && _d !== void 0 ? _d : 0,
+            scenarios: exclude.flatMap((pg) => {
+                return pg.scenarios.map((plan) => {
+                    return {
+                        endpoint: pg.endpoint,
+                        draft: plan.draft,
+                        functionName: plan.functionName,
+                        dependencies: plan.dependsOn,
+                    };
+                });
+            }),
+            created_at: new Date().toISOString(),
         };
     });
 }
-function process(ctx, endpoint, endpoints, files) {
-    return __awaiter(this, void 0, void 0, function* () {
-        var _a;
-        const pointer = {
-            value: null,
-        };
-        const agentica = new core_1.MicroAgentica({
-            model: ctx.model,
-            vendor: ctx.vendor,
-            config: Object.assign(Object.assign({}, ((_a = ctx.config) !== null && _a !== void 0 ? _a : { locale: "en-US" })), { systemPrompt: {
-                    describe: () => {
-                        return "Answer only 'completion' or 'failure'.";
-                    },
-                } }),
-            tokenUsage: ctx.usage(),
-            histories: [
-                ...(0, transformTestScenarioHistories_1.transformTestScenarioHistories)(ctx.state(), endpoints, files),
-            ],
-            controllers: [
-                createApplication({
-                    model: ctx.model,
-                    build: (next) => {
-                        pointer.value = next.scenarios;
-                    },
-                }),
-            ],
-        });
-        agentica.on("request", (event) => __awaiter(this, void 0, void 0, function* () {
-            if (event.body.tools)
-                event.body.tool_choice = "required";
-        }));
-        yield agentica.conversate([
-            "Make User Scenarios for below endpoint:",
+const execute = (ctx, ops, include, exclude) => __awaiter(void 0, void 0, void 0, function* () {
+    var _a;
+    const pointer = {
+        value: [],
+    };
+    const agentica = new core_1.MicroAgentica({
+        model: ctx.model,
+        vendor: ctx.vendor,
+        config: Object.assign(Object.assign({}, ((_a = ctx.config) !== null && _a !== void 0 ? _a : {})), { executor: {
+                describe: null,
+            } }),
+        tokenUsage: ctx.usage(),
+        histories: createHistoryProperties(ops, include, exclude),
+        controllers: [
+            createApplication({
+                model: ctx.model,
+                build: (next) => {
+                    var _a;
+                    (_a = pointer.value) !== null && _a !== void 0 ? _a : (pointer.value = []);
+                    pointer.value.push(...next.scenarioGroups);
+                },
+            }),
+        ],
+    });
+    (0, enforceToolCall_1.enforceToolCall)(agentica);
+    yield agentica.conversate(`create test scenarios.`);
+    if (pointer.value.length === 0) {
+        throw new Error("Failed to create test plans.");
+    }
+    return pointer.value;
+});
+const createHistoryProperties = (operations, include, exclude) => [
+    {
+        id: (0, uuid_1.v4)(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: "You are the AutoAPI Test Scenario Generator.\n\nYour job is to analyze an array of API operation objects and generate realistic, structured test scenario drafts for each operation.\n\n---\n\n## Input Format\n\nYou will receive an array of `Operation` objects structured like this:\n\n```ts\n{\n  method: \"post\" | \"get\" | \"put\" | \"patch\" | \"delete\",\n  path: \"/path/to/resource\",\n  specification: string,     // API specification with business logic and constraints\n  description: string,       // Multi-paragraph description\n  summary: string,           // One-line summary\n  parameters: [...],         // List of path/query/body parameters\n  requestBody?: {\n    typeName: string,\n    description: string\n  },\n  responseBody: {\n    typeName: string,\n    description: string\n  }\n}\n```\n\n---\n\n## Output Format\n\nYour output must be an array of grouped test plans, using the following structure:\n\n```ts\n[\n  {\n    method: \"post\",\n    path: \"/shopping/products\",\n    plans: [\n      {\n        draft: \"Test product creation by submitting two requests with the same product.pid. Confirm that the second request returns a uniqueness constraint error.\",\n        dependsOn: [\n          {\n            method: \"post\",\n            path: \"/shopping/categories\",\n            purpose: \"Create a category beforehand so the product can reference it.\"\n          },\n          {\n            method: \"get\",\n            path: \"/users/me\",\n            purpose: \"Verify a valid user session and obtain user context for the test.\"\n          }\n        ]\n      },\n      {\n        draft: \"Verify that missing required fields like 'name' or 'price' trigger appropriate validation errors.\",\n        dependsOn: []\n      }\n    ]\n  },\n  {\n    method: \"patch\",\n    path: \"/shopping/products/{productId}\",\n    plans: [\n      {\n        draft: \"Attempt to update a product with an invalid productId and expect a 404 error.\",\n        dependsOn: []\n      }\n    ]\n  }\n]\n```\n\n- Each top-level object is a **plan group** for a single unique endpoint (`method + path`).\n- The `plans` array contains **one or more test drafts** for that endpoint.\n- Each `draft` may list its **prerequisite API calls** in the `dependsOn` array, which includes `method`, `path`, and a `purpose` for context.\n\n---\n\n### \u2705 **Uniqueness Rule**\n\n> \u26A0\uFE0F **Each `{method} + {path}` combination must appear only once** in the output array.\n> This means **you must not create multiple plan groups with the same HTTP method and path.**\n\n* Treat each `{method} + {path}` pair as a **unique test identifier**.\n* All test plans (`plans`) related to the same endpoint must be **grouped under a single PlanGroup object**.\n* Duplicating PlanGroups for the same endpoint will lead to invalid output.\n\n**\u2705 Good:**\n\n```ts\n[\n  {\n    method: \"patch\",\n    path: \"/blog/posts/{postId}\",\n    plans: [\n      { draft: \"...\", dependsOn: [...] },\n      { draft: \"...\", dependsOn: [...] }\n    ]\n  }\n]\n```\n\n**\u274C Bad:**\n\n```ts\n[\n  {\n    method: \"patch\",\n    path: \"/blog/posts/{postId}\",\n    plans: [ ... ]\n  },\n  {\n    method: \"patch\",\n    path: \"/blog/posts/{postId}\", // Duplicate! Not allowed.\n    plans: [ ... ]\n  }\n]\n```\n\n---\n\n## Writing Guidelines\n\n1. **draft**:\n   - Write a clear and realistic test plan for the operation.\n   - Include both success and failure cases where applicable.\n   - Incorporate constraints mentioned in the API description such as uniqueness, foreign key requirements, or authentication.\n   - For complex operations, include multiple steps within the same `draft` string (e.g., create \u2192 verify \u2192 delete).\n\n2. **dependsOn**:\n   - List other API operations that must be invoked before this test can be executed.\n   - Each item must include `method`, `path`, and `purpose`.\n   - The `purpose` field should explain *why* the dependency is needed in the test setup.\n\n3. Treat each `{method} + {path}` combination as a unique test identifier.\n\n---\n\n## Purpose\n\nThese test scenario objects are designed to support QA engineers and backend developers in planning automated or manual tests. Each test draft reflects the core functionality and business rules of the API to ensure robust system behavior." /* AutoBeSystemPromptConstant.TEST_SCENARIO */,
+    },
+    {
+        id: (0, uuid_1.v4)(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+            "Below are the full operations. Please refer to this.",
+            "Your role is to draft all test cases for each given Operation.",
+            "It is also permissible to write multiple test codes on a single endpoint.",
+            "However, rather than meaningless tests, business logic tests should be written and an E2E test situation should be assumed.",
             "",
             "```json",
-            JSON.stringify(endpoint, null, 2),
+            JSON.stringify(operations.map((el) => ({
+                path: el.path,
+                method: el.method,
+                summary: el.summary,
+            }))),
             "```",
-        ].join("\n"));
-        if (pointer.value === null)
-            throw new Error("Failed to make scenarios.");
-        return pointer.value;
-    });
-}
+        ].join("\n"),
+    },
+    {
+        id: (0, uuid_1.v4)(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+            "# Included in Test Plan",
+            include
+                .map((el) => `- ${el.method.toUpperCase()}: ${el.path}`)
+                .join("\n"),
+            "",
+            "# 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.",
+            exclude
+                .map((el) => `- ${el.method.toUpperCase()}: ${el.path}`)
+                .join("\n"),
+        ].join("\n"),
+    },
+];
 function createApplication(props) {
     (0, assertSchemaModel_1.assertSchemaModel)(props.model);
     const application = collection[props.model];
+    application.functions[0].validate = (next) => {
+        const result = (() => { const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every(elem => "object" === typeof elem && null !== elem && _io4(elem))); const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
+            })) && input.scenarioGroups.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                value: elem
+            })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                value: elem
+            })).every(flag => flag) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
+            })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                value: input.scenarios
+            })) && input.scenarios.map((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
+                value: elem
+            })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", true && _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
+                value: elem
+            })).every(flag => flag) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                value: input.scenarios
+            })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.path || _report(_exceptionable, {
+                path: _path + ".path",
+                expected: "string",
+                value: input.path
+            }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                path: _path + ".method",
+                expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
+                value: input.method
+            })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.draft || _report(_exceptionable, {
+                path: _path + ".draft",
+                expected: "string",
+                value: input.draft
+            }), "string" === typeof input.functionName || _report(_exceptionable, {
+                path: _path + ".functionName",
+                expected: "string",
+                value: input.functionName
+            }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            })) && input.dependsOn.map((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", true && _exceptionable) || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            })).every(flag => flag) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), "string" === typeof input.purpose || _report(_exceptionable, {
+                path: _path + ".purpose",
+                expected: "string",
+                value: input.purpose
+            })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
+            if (false === __is(input)) {
+                errors = [];
+                _report = __typia_transform__validateReport._validateReport(errors);
+                ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                    path: _path + "",
+                    expected: "IAutoBeTestScenarioApplication.IProps",
+                    value: input
+                })) && _vo0(input, _path + "", true) || _report(true, {
+                    path: _path + "",
+                    expected: "IAutoBeTestScenarioApplication.IProps",
+                    value: input
+                }))(input, "$input", true);
+                const success = 0 === errors.length;
+                return success ? {
+                    success,
+                    data: input
+                } : {
+                    success,
+                    errors,
+                    data: input
+                };
+            }
+            return {
+                success: true,
+                data: input
+            };
+        }; })()(next);
+        if (result.success === false)
+            return result;
+        const errors = [];
+        result.data.scenarioGroups.forEach((pg, i, arr) => {
+            arr.forEach((target, j) => {
+                if (i !== j &&
+                    target.endpoint.method === pg.endpoint.method &&
+                    target.endpoint.path === pg.endpoint.path) {
+                    if (!errors.some((el) => el.path !== `planGroups[${j}].path` &&
+                        el.value !== target.endpoint.path)) {
+                        errors.push({
+                            path: `planGroups[${j}].path`,
+                            expected: `planGroup's {method + path} cannot duplicated.`,
+                            value: target.endpoint.path,
+                        });
+                    }
+                    if (!errors.some((el) => el.path !== `planGroups[${j}].method` &&
+                        el.value !== target.endpoint.method)) {
+                        errors.push({
+                            path: `planGroups[${j}].method`,
+                            expected: `planGroup's {method + path} cannot duplicated.`,
+                            value: target.endpoint.method,
+                        });
+                    }
+                }
+            });
+        });
+        if (errors.length !== 0) {
+            console.log(JSON.stringify(errors, null, 2), "errors");
+            return {
+                success: false,
+                errors,
+                data: next,
+            };
+        }
+        return result;
+    };
     return {
         protocol: "class",
-        name: "Make User Scenarios",
+        name: "Make test plans",
         application,
         execute: {
             makeScenario: (next) => {
@@ -166,19 +342,19 @@ const claude = {
         {
             name: "makeScenario",
             parameters: {
-                description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
                 type: "object",
                 properties: {
-                    scenarios: {
-                        title: "Array of user scenarios",
-                        description: "Array of user scenarios.",
+                    scenarioGroups: {
+                        title: "Array of test scenario groups",
+                        description: "Array of test scenario groups.",
                         type: "array",
                         items: {
-                            description: "Current Type: {@link AutoBeTest.IScenario}",
+                            description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
                             type: "object",
                             properties: {
                                 endpoint: {
-                                    description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                    description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
                                     type: "object",
                                     properties: {
                                         path: {
@@ -214,26 +390,81 @@ const claude = {
                                     ]
                                 },
                                 scenarios: {
-                                    title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                    description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
+                                    title: "Array of test scenarios",
+                                    description: "Array of test scenarios.",
                                     type: "array",
                                     items: {
-                                        description: "Current Type: {@link AutoBeTest.Scenario}",
+                                        description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
                                         type: "object",
                                         properties: {
+                                            draft: {
+                                                description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios.",
+                                                type: "string"
+                                            },
                                             functionName: {
                                                 title: "Descriptive function name derived from the user scenario",
                                                 description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
                                                 type: "string"
                                             },
-                                            scenario: {
-                                                description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
-                                                type: "string"
+                                            dependsOn: {
+                                                description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state.",
+                                                type: "array",
+                                                items: {
+                                                    description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                    type: "object",
+                                                    properties: {
+                                                        endpoint: {
+                                                            description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                            type: "object",
+                                                            properties: {
+                                                                path: {
+                                                                    title: "HTTP path of the API operation",
+                                                                    description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                                                    type: "string"
+                                                                },
+                                                                method: {
+                                                                    title: "HTTP method of the API operation",
+                                                                    description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                                                    oneOf: [
+                                                                        {
+                                                                            "const": "get"
+                                                                        },
+                                                                        {
+                                                                            "const": "post"
+                                                                        },
+                                                                        {
+                                                                            "const": "put"
+                                                                        },
+                                                                        {
+                                                                            "const": "delete"
+                                                                        },
+                                                                        {
+                                                                            "const": "patch"
+                                                                        }
+                                                                    ]
+                                                                }
+                                                            },
+                                                            required: [
+                                                                "path",
+                                                                "method"
+                                                            ]
+                                                        },
+                                                        purpose: {
+                                                            description: "A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: \"Creates a category so that a product can be linked to it during\ncreation.\"",
+                                                            type: "string"
+                                                        }
+                                                    },
+                                                    required: [
+                                                        "endpoint",
+                                                        "purpose"
+                                                    ]
+                                                }
                                             }
                                         },
                                         required: [
+                                            "draft",
                                             "functionName",
-                                            "scenario"
+                                            "dependsOn"
                                         ]
                                     }
                                 }
@@ -246,28 +477,28 @@ const claude = {
                     }
                 },
                 required: [
-                    "scenarios"
+                    "scenarioGroups"
                 ],
                 additionalProperties: false,
                 $defs: {}
             },
-            description: "Make user scenarios for the given endpoints.",
-            validate: (() => { const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarios) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
-                })) && input.scenarios.map((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
+            description: "Make test scenarios for the given endpoints.",
+            validate: (() => { const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every(elem => "object" === typeof elem && null !== elem && _io4(elem))); const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
+                })) && input.scenarioGroups.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                     value: elem
-                })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", true && _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
+                })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                     value: elem
                 })).every(flag => flag) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
                 })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
                     path: _path + ".endpoint",
                     expected: "AutoBeOpenApi.IEndpoint",
@@ -278,19 +509,19 @@ const claude = {
                     value: input.endpoint
                 }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
                     path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                     value: input.scenarios
-                })) && input.scenarios.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
+                })) && input.scenarios.map((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
                     value: elem
-                })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
+                })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", true && _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
                     value: elem
                 })).every(flag => flag) || _report(_exceptionable, {
                     path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                     value: input.scenarios
                 })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.path || _report(_exceptionable, {
                     path: _path + ".path",
@@ -300,25 +531,53 @@ const claude = {
                     path: _path + ".method",
                     expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
                     value: input.method
-                })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.functionName || _report(_exceptionable, {
+                })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.draft || _report(_exceptionable, {
+                    path: _path + ".draft",
+                    expected: "string",
+                    value: input.draft
+                }), "string" === typeof input.functionName || _report(_exceptionable, {
                     path: _path + ".functionName",
                     expected: "string",
                     value: input.functionName
-                }), "string" === typeof input.scenario || _report(_exceptionable, {
-                    path: _path + ".scenario",
+                }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                })) && input.dependsOn.map((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", true && _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                })).every(flag => flag) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), "string" === typeof input.purpose || _report(_exceptionable, {
+                    path: _path + ".purpose",
                     expected: "string",
-                    value: input.scenario
+                    value: input.purpose
                 })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
                 if (false === __is(input)) {
                     errors = [];
                     _report = __typia_transform__validateReport._validateReport(errors);
                     ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                         path: _path + "",
-                        expected: "IMakeScenarioProps",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
                         value: input
                     })) && _vo0(input, _path + "", true) || _report(true, {
                         path: _path + "",
-                        expected: "IMakeScenarioProps",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
                         value: input
                     }))(input, "$input", true);
                     const success = 0 === errors.length;
@@ -351,19 +610,19 @@ const collection = {
             {
                 name: "makeScenario",
                 parameters: {
-                    description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                    description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
                     type: "object",
                     properties: {
-                        scenarios: {
-                            title: "Array of user scenarios",
-                            description: "Array of user scenarios.",
+                        scenarioGroups: {
+                            title: "Array of test scenario groups",
+                            description: "Array of test scenario groups.",
                             type: "array",
                             items: {
-                                description: "Current Type: {@link AutoBeTest.IScenario}",
+                                description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
                                 type: "object",
                                 properties: {
                                     endpoint: {
-                                        description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                        description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
                                         type: "object",
                                         properties: {
                                             path: {
@@ -390,26 +649,72 @@ const collection = {
                                         ]
                                     },
                                     scenarios: {
-                                        title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                        description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
+                                        title: "Array of test scenarios",
+                                        description: "Array of test scenarios.",
                                         type: "array",
                                         items: {
-                                            description: "Current Type: {@link AutoBeTest.Scenario}",
+                                            description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
                                             type: "object",
                                             properties: {
+                                                draft: {
+                                                    description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios.",
+                                                    type: "string"
+                                                },
                                                 functionName: {
                                                     title: "Descriptive function name derived from the user scenario",
                                                     description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
                                                     type: "string"
                                                 },
-                                                scenario: {
-                                                    description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
-                                                    type: "string"
+                                                dependsOn: {
+                                                    description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state.",
+                                                    type: "array",
+                                                    items: {
+                                                        description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                        type: "object",
+                                                        properties: {
+                                                            endpoint: {
+                                                                description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                                type: "object",
+                                                                properties: {
+                                                                    path: {
+                                                                        title: "HTTP path of the API operation",
+                                                                        description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                                                        type: "string"
+                                                                    },
+                                                                    method: {
+                                                                        title: "HTTP method of the API operation",
+                                                                        description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                                                        type: "string",
+                                                                        "enum": [
+                                                                            "get",
+                                                                            "post",
+                                                                            "put",
+                                                                            "delete",
+                                                                            "patch"
+                                                                        ]
+                                                                    }
+                                                                },
+                                                                required: [
+                                                                    "path",
+                                                                    "method"
+                                                                ]
+                                                            },
+                                                            purpose: {
+                                                                description: "A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: \"Creates a category so that a product can be linked to it during\ncreation.\"",
+                                                                type: "string"
+                                                            }
+                                                        },
+                                                        required: [
+                                                            "endpoint",
+                                                            "purpose"
+                                                        ]
+                                                    }
                                                 }
                                             },
                                             required: [
+                                                "draft",
                                                 "functionName",
-                                                "scenario"
+                                                "dependsOn"
                                             ]
                                         }
                                     }
@@ -422,28 +727,28 @@ const collection = {
                         }
                     },
                     required: [
-                        "scenarios"
+                        "scenarioGroups"
                     ],
                     additionalProperties: false,
                     $defs: {}
                 },
-                description: "Make user scenarios for the given endpoints.",
-                validate: (() => { const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarios) || _report(_exceptionable, {
-                        path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.IScenario>",
-                        value: input.scenarios
-                    })) && input.scenarios.map((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index3 + "]",
-                        expected: "AutoBeTest.IScenario",
+                description: "Make test scenarios for the given endpoints.",
+                validate: (() => { const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every(elem => "object" === typeof elem && null !== elem && _io4(elem))); const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                        value: input.scenarioGroups
+                    })) && input.scenarioGroups.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups[" + _index4 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                         value: elem
-                    })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", true && _exceptionable) || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index3 + "]",
-                        expected: "AutoBeTest.IScenario",
+                    })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups[" + _index4 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                         value: elem
                     })).every(flag => flag) || _report(_exceptionable, {
-                        path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.IScenario>",
-                        value: input.scenarios
+                        path: _path + ".scenarioGroups",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                        value: input.scenarioGroups
                     })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
                         path: _path + ".endpoint",
                         expected: "AutoBeOpenApi.IEndpoint",
@@ -454,19 +759,19 @@ const collection = {
                         value: input.endpoint
                     }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
                         path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.Scenario>",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                         value: input.scenarios
-                    })) && input.scenarios.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index4 + "]",
-                        expected: "AutoBeTest.Scenario",
+                    })) && input.scenarios.map((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".scenarios[" + _index5 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenario",
                         value: elem
-                    })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index4 + "]",
-                        expected: "AutoBeTest.Scenario",
+                    })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".scenarios[" + _index5 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenario",
                         value: elem
                     })).every(flag => flag) || _report(_exceptionable, {
                         path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.Scenario>",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                         value: input.scenarios
                     })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.path || _report(_exceptionable, {
                         path: _path + ".path",
@@ -476,25 +781,53 @@ const collection = {
                         path: _path + ".method",
                         expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
                         value: input.method
-                    })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.functionName || _report(_exceptionable, {
+                    })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.draft || _report(_exceptionable, {
+                        path: _path + ".draft",
+                        expected: "string",
+                        value: input.draft
+                    }), "string" === typeof input.functionName || _report(_exceptionable, {
                         path: _path + ".functionName",
                         expected: "string",
                         value: input.functionName
-                    }), "string" === typeof input.scenario || _report(_exceptionable, {
-                        path: _path + ".scenario",
+                    }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                        path: _path + ".dependsOn",
+                        expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                        value: input.dependsOn
+                    })) && input.dependsOn.map((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".dependsOn[" + _index6 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                        value: elem
+                    })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".dependsOn[" + _index6 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                        value: elem
+                    })).every(flag => flag) || _report(_exceptionable, {
+                        path: _path + ".dependsOn",
+                        expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                        value: input.dependsOn
+                    })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                        path: _path + ".endpoint",
+                        expected: "AutoBeOpenApi.IEndpoint",
+                        value: input.endpoint
+                    })) && _vo2(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".endpoint",
+                        expected: "AutoBeOpenApi.IEndpoint",
+                        value: input.endpoint
+                    }), "string" === typeof input.purpose || _report(_exceptionable, {
+                        path: _path + ".purpose",
                         expected: "string",
-                        value: input.scenario
+                        value: input.purpose
                     })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
                     if (false === __is(input)) {
                         errors = [];
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -532,7 +865,7 @@ const collection = {
                 parameters: {
                     type: "object",
                     properties: {
-                        scenarios: {
+                        scenarioGroups: {
                             type: "array",
                             items: {
                                 type: "object",
@@ -562,7 +895,7 @@ const collection = {
                                             "path",
                                             "method"
                                         ],
-                                        description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                        description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
                                         additionalProperties: false
                                     },
                                     scenarios: {
@@ -570,61 +903,109 @@ const collection = {
                                         items: {
                                             type: "object",
                                             properties: {
+                                                draft: {
+                                                    type: "string",
+                                                    description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios."
+                                                },
                                                 functionName: {
                                                     type: "string",
                                                     title: "Descriptive function name derived from the user scenario",
                                                     description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions"
                                                 },
-                                                scenario: {
-                                                    type: "string",
-                                                    description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description"
+                                                dependsOn: {
+                                                    type: "array",
+                                                    items: {
+                                                        type: "object",
+                                                        properties: {
+                                                            endpoint: {
+                                                                type: "object",
+                                                                properties: {
+                                                                    path: {
+                                                                        type: "string",
+                                                                        title: "HTTP path of the API operation",
+                                                                        description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage."
+                                                                    },
+                                                                    method: {
+                                                                        type: "string",
+                                                                        "enum": [
+                                                                            "get",
+                                                                            "post",
+                                                                            "put",
+                                                                            "delete",
+                                                                            "patch"
+                                                                        ],
+                                                                        title: "HTTP method of the API operation",
+                                                                        description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
+                                                                    }
+                                                                },
+                                                                required: [
+                                                                    "path",
+                                                                    "method"
+                                                                ],
+                                                                description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                                additionalProperties: false
+                                                            },
+                                                            purpose: {
+                                                                type: "string",
+                                                                description: "A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: \"Creates a category so that a product can be linked to it during\ncreation.\""
+                                                            }
+                                                        },
+                                                        required: [
+                                                            "endpoint",
+                                                            "purpose"
+                                                        ],
+                                                        description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                        additionalProperties: false
+                                                    },
+                                                    description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state."
                                                 }
                                             },
                                             required: [
+                                                "draft",
                                                 "functionName",
-                                                "scenario"
+                                                "dependsOn"
                                             ],
-                                            description: "Current Type: {@link AutoBeTest.Scenario}",
+                                            description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
                                             additionalProperties: false
                                         },
-                                        title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                        description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts"
+                                        title: "Array of test scenarios",
+                                        description: "Array of test scenarios."
                                     }
                                 },
                                 required: [
                                     "endpoint",
                                     "scenarios"
                                 ],
-                                description: "Current Type: {@link AutoBeTest.IScenario}",
+                                description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
                                 additionalProperties: false
                             },
-                            title: "Array of user scenarios",
-                            description: "Array of user scenarios."
+                            title: "Array of test scenario groups",
+                            description: "Array of test scenario groups."
                         }
                     },
                     required: [
-                        "scenarios"
+                        "scenarioGroups"
                     ],
-                    description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                    description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
                     additionalProperties: false
                 },
-                description: "Make user scenarios for the given endpoints.",
-                validate: (() => { const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarios) || _report(_exceptionable, {
-                        path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.IScenario>",
-                        value: input.scenarios
-                    })) && input.scenarios.map((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index3 + "]",
-                        expected: "AutoBeTest.IScenario",
+                description: "Make test scenarios for the given endpoints.",
+                validate: (() => { const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every(elem => "object" === typeof elem && null !== elem && _io1(elem)); const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every(elem => "object" === typeof elem && null !== elem && _io3(elem))); const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every(elem => "object" === typeof elem && null !== elem && _io4(elem))); const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose; const _vo0 = (input, _path, _exceptionable = true) => [(Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                        value: input.scenarioGroups
+                    })) && input.scenarioGroups.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups[" + _index4 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                         value: elem
-                    })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", true && _exceptionable) || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index3 + "]",
-                        expected: "AutoBeTest.IScenario",
+                    })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".scenarioGroups[" + _index4 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                         value: elem
                     })).every(flag => flag) || _report(_exceptionable, {
-                        path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.IScenario>",
-                        value: input.scenarios
+                        path: _path + ".scenarioGroups",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                        value: input.scenarioGroups
                     })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
                         path: _path + ".endpoint",
                         expected: "AutoBeOpenApi.IEndpoint",
@@ -635,19 +1016,19 @@ const collection = {
                         value: input.endpoint
                     }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
                         path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.Scenario>",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                         value: input.scenarios
-                    })) && input.scenarios.map((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index4 + "]",
-                        expected: "AutoBeTest.Scenario",
+                    })) && input.scenarios.map((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".scenarios[" + _index5 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenario",
                         value: elem
-                    })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", true && _exceptionable) || _report(_exceptionable, {
-                        path: _path + ".scenarios[" + _index4 + "]",
-                        expected: "AutoBeTest.Scenario",
+                    })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".scenarios[" + _index5 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IScenario",
                         value: elem
                     })).every(flag => flag) || _report(_exceptionable, {
                         path: _path + ".scenarios",
-                        expected: "Array<AutoBeTest.Scenario>",
+                        expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                         value: input.scenarios
                     })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.path || _report(_exceptionable, {
                         path: _path + ".path",
@@ -657,25 +1038,53 @@ const collection = {
                         path: _path + ".method",
                         expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
                         value: input.method
-                    })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.functionName || _report(_exceptionable, {
+                    })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.draft || _report(_exceptionable, {
+                        path: _path + ".draft",
+                        expected: "string",
+                        value: input.draft
+                    }), "string" === typeof input.functionName || _report(_exceptionable, {
                         path: _path + ".functionName",
                         expected: "string",
                         value: input.functionName
-                    }), "string" === typeof input.scenario || _report(_exceptionable, {
-                        path: _path + ".scenario",
+                    }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                        path: _path + ".dependsOn",
+                        expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                        value: input.dependsOn
+                    })) && input.dependsOn.map((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                        path: _path + ".dependsOn[" + _index6 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                        value: elem
+                    })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".dependsOn[" + _index6 + "]",
+                        expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                        value: elem
+                    })).every(flag => flag) || _report(_exceptionable, {
+                        path: _path + ".dependsOn",
+                        expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                        value: input.dependsOn
+                    })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                        path: _path + ".endpoint",
+                        expected: "AutoBeOpenApi.IEndpoint",
+                        value: input.endpoint
+                    })) && _vo2(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                        path: _path + ".endpoint",
+                        expected: "AutoBeOpenApi.IEndpoint",
+                        value: input.endpoint
+                    }), "string" === typeof input.purpose || _report(_exceptionable, {
+                        path: _path + ".purpose",
                         expected: "string",
-                        value: input.scenario
+                        value: input.purpose
                     })].every(flag => flag); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
                     if (false === __is(input)) {
                         errors = [];
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;