Assertions

Assertions define what a correct result looks like. After Spark runs the execution, it checks each assertion against the actual response. All of them must pass for the test to pass.

Every assertion is evaluated, even if an earlier one fails. This means you see all problems at once rather than fixing them one at a time. No more whack-a-mole debugging.

assertions:
  - statusCode:
      equals: 200

assertions:
  - exitCode:
      equals: 0
  - stdout:
      contains: "Success"
  - stderr:
      equals: ""

Which assertions can I use?

It depends on the executor type:

Assertion	HTTP	CLI	What it checks
`statusCode`	yes	—	HTTP response status code
`jsonPath`	yes	—	Values inside JSON response body
`exitCode`	—	yes	Command exit code
`stdout`	—	yes	Standard output content
`stderr`	—	yes	Standard error content
`snapshot`	yes	yes	Compare against a saved reference file