Test Scenario Modeling

Prerequisite: read ../apidog-cli/SKILL.md first. If the stable entry skill conflicts with this domain skill, use the current CLI help and this skill as the source of truth. For single-endpoint cases, read ../apidog-test-case/SKILL.md; for execution, CI, and report boundaries, read ../apidog-test-automation/SKILL.md. Environment and variable commands follow current CLI help.

Always use current CLI help for exact arguments. When creating or updating test scenarios, focus on step persistence semantics, import/reference boundaries, variable passing, complex step field risks, and run-time verification. Agents should prefer import/reference commands and get --with-case-detail to read the real structure before making local updates.

When To Use

• Create or update test scenarios.
• Design multi-step automated flows such as login -> create resource -> query -> assert -> cleanup.
• Orchestrate step types such as conditions, loops, waits, scripts, database operations, or external programs.
• Handle pre/post actions, variable references, variable extractors, and assertion chains.
• Diagnose scenario step linkage failures, empty variables, wrong step order, or client display issues after scenario creation.

When Not To Use