Scenarios
Scenarios lists the API scenarios this workspace has saved to AutoRunner.
A generated scenario stays a draft inside its session until you save it. Saving copies it into an AutoRunner folder as an independent scenario — this page is where those saved scenarios live afterwards.
The explorer
The left panel is a folder tree of the AutoRunner source projects scenarios were saved into, with a search box and a filter. Until something has been saved it reads No source projects; the detail panel prompts you to expand a source folder and pick a scenario.
+ New Scenario creates a scenario directly in SmartAPI's saved tree, starting from one empty request — useful when you want to write a check by hand rather than generate it.
Reviewing a scenario
Selecting a scenario opens it with its step count, assertions, and captures, and the steps laid out in order. Each step has its own tabs:
| Tab | Contents |
|---|---|
| Request | The API request, as JSON |
| Checks & extraction | Response checks and the values captured from the response |
| Scripts | Pre-request and post-response scripts |
| Variables | Scenario variables and their initial values |
Scripts write named checks with rq.test in JavaScript. Variables set initial values here; scripts
and response extraction can replace them while the scenario runs.
Regenerating
From any step, Regenerate from here rewrites that step and everything after it while leaving earlier steps untouched; draft edits are saved first. Regenerate automation rewrites the whole scenario.
Some saved scenarios have no editable API automation. Those open read-only with a pointer to AutoRunner, where they can be reviewed or regenerated instead.
Unsaved edits prompt before they are discarded.
Next Steps
- API Test Generation — Produce the scenarios that land here
- AutoRunner Transfer — How saved scenarios reach an AutoRunner project
- AutoRunner — Run them
