Assertions

Assertions are checks that prove a journey behaved as expected. They turn a run from a recorded sequence into evidence.

Common assertions

• Response status matches the expected code.
• A JSON field exists or has an expected value.
• A response time stays within a threshold.
• A saved output is present.
• A downstream state change can be observed.

Coverage

Assertions can be mapped to acceptance criteria so teams can see what has proof and what still needs coverage.