Requests, Assertions, and Captures

Open a generated candidate from Sessions, or a saved scenario from Scenarios, then expand a request. The current request editor provides Assertions, Captures, Body, Headers, Params, and Scripts tabs. Generated requests can also show Plan step for comparison with the intended workflow.

Request body

Use Body to review the request payload and its representation. Match the content type to the body format, check required fields, and replace literal secrets with variables.

Headers and parameters

Use Headers and Params to inspect and edit request inputs. Check names, values, encoding, and any contract requirement for repeated query keys. Add only headers required by the API, and supply authorization values through variables rather than literal credentials.

Assertions

Assertions lists response checks with their Type, Path, Operator, and Expected value. Checks can cover status, a JSON path, a header, the body, or response time.

Use Add assertion for another check. Edit JSON exposes its underlying definition when a structured row is not sufficient.

Review each assertion for a meaningful expected value and operator. An existence check should test something the contract guarantees; exact equality should not depend on a changing timestamp or a coincidental example value.

Captures

Captures lists a variable Name, response Source, and Path. Captures can read a JSON path, header, cookie, or body. Use Add capture to extract another value for later requests.

Ensure the producing request runs first, the response field exists on success, and the variable name matches every later reference. Keep unrelated values under different names.

Scripts

Scripts contains pre-request and post-response JavaScript. Named response tests use rq.test. Review the scripts together with assertions and captures so they do not duplicate or contradict one another. Avoid logging secrets or adding unreviewed side effects.

Save the reviewed automation

Review all changed requests before saving. On a generated session candidate, Regenerate from here replaces the current request and later requests; inspect the new checks and captures again afterwards. Saved scenarios use Save Changes and Discard changes and have no regeneration control.

Keep real credentials in the execution environment. See Variables and Environment Input for reusable values and AutoRunner Transfer for saving a reviewed candidate.