Variables and Environment Input

Variables provide reusable values for a scenario's requests, assertions, and scripts. Open Variables on a generated scenario to inspect its initial values; use Captures on a request for values extracted from a response.

Initial variables

The variable editor shows Name, Type, Value, and Secret, with an Add variable action. Use recognizable names and safe example defaults. A secret field can be masked; masking is not a substitute for keeping real credentials out of documentation and generated examples.

Variables belong to the scenario being reviewed. Check every reference against that scenario's initial values and the captures produced by its earlier requests.

On a saved scenario, Variables opens the shared AutoRunner variable panel, which includes scenario values and Workspace values. It uses the AutoRunner variable controls rather than the generated candidate's Name, Type, Value, and Secret sheet.

Response-derived values

The request's Captures tab extracts values from a JSON path, header, cookie, or response body. For example, a create request can capture createdOrderId for the next request to use.

Verify that the capture runs before its consumer and that negative cases cannot overwrite a value needed by later steps. See Requests, Assertions, and Captures.

Runtime environments

SmartAPI's current navigation has no standalone environment manager. After saving a scenario, configure runtime values and secrets through AutoRunner Test Datas and Run Profiles.

A Postman environment is not a separate managed source type in the current SmartAPI file filter. Use File Management for supported API sources and AutoRunner for execution environments.