Skip to main content
Version: 1.0.8

Generated Tests and Flows

A generation session contains scenario candidates and their ordered API requests. Open the run from Sessions, then select a scenario to inspect its automation.

Review a candidate​

Check the scenario's name, description, generation state, and request order. A scenario can contain multiple requests, response assertions, captured values, scripts, and variables.

Expand the scenario to follow its request sequence, or open its details to review one request at a time. Compare the planned steps with the generated automation before saving.

The older session-wide Test Cases and Flows screens are replaced by scenario review. API-level service maps, flows, and relationships are inspected in Inventory and discovery.

Review the sequence​

For each scenario:

  1. Confirm its business purpose and the expected positive or negative behavior.
  2. Compare every method and path with the selected source version.
  3. Place authentication and setup before protected operations.
  4. Ensure a captured value is produced before a later request uses it.
  5. Review response checks, variables, and scripts.
  6. Check that cleanup requests affect only data created by this scenario.

Editing or saving automation does not prove that it has executed successfully.

Save and regenerate​

Save scenario creates an independent AutoRunner scenario in the folder you choose. The generated candidate remains available; saving it again creates another copy.

Regenerate from here rewrites the selected request and the requests after it, preserving earlier steps; Regenerate automation starts again from the first step. Draft edits are saved before regeneration. These actions require a generated candidate and the relevant permissions; a manually added candidate has no generation to rerun. Review the replacement before saving it.

A saved copy is edited independently under Scenarios, with Save Changes and Discard changes instead of regeneration controls.

Saved scenarios​

Saved copies are listed in the workspace's Scenarios explorer, grouped by AutoRunner source and folder.

Current saved-scenario explorer

An empty explorer shows No source projects. Select a saved scenario to review its automation; the request editor is unavailable for scenarios without a compatible API automation document.

Continue with Requests, Assertions, and Captures for request-level review.