Tests and simulations

Tests and simulations show what a policy would decide for a specified request. They do not execute an action, create a live decision or approval request, or reserve usage capacity.

Save tests with a policy

Open a policy’s Tests section. Add a request, name the scenario, and set the expected result: Allow, Require approval, Block, or No match.

Start with a captured request when possible. Preserve the structure and types of the fields the integration sends, then change the values that exercise the rule. Include:

• Requests inside and outside the policy scope.
• Values below, at, and above each threshold.
• Missing or unexpected input where it is relevant to the control.
• Different counter balances, including pending usage.
• Requests that match more than one rule.

The editor previews tests as you work. Run checks in Review and publish validates the saved revision before publication.

Explore a request in Simulations

Open Simulations, choose a policy, and select a saved test or recent decision. Adjust the request and inspect how the draft compares with the published version.

Use this to answer concrete questions, such as whether changing a refund threshold would require approval for a previously allowed request. Save a useful scenario as a policy test so it is checked again during future edits.

Read the result

A policy test reports No match when its scope or rules do not decide the request. It does not substitute the selected agent’s fallback or prove the combined result of every assigned policy.

Inspect which conditions matched, which effect took precedence, the reason, and the approval group. Matching lower-priority rules can remain visible even when a Block determines the outcome.

For counters, provide representative values for settled, held, current, delta, and projected. Current usage is settled plus held; projected usage adds the request’s contribution.

A passing test cannot reserve capacity for a later live request. After publication, send controlled requests through the integration and inspect their decisions to verify assignment, mode, fallback, and execution reporting together.