Pure checks for Retry Policy

Verification Boundary

The suite checks deterministic module behavior and declared configuration using local inputs.

What This Suite Proves

Retry classification separates recoverable faults. Depleted provider credit does not retry. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

These checks do not establish database transactions, deployed permissions, provider availability or a complete user journey.

Real Dependencies and Test Doubles

The classifier and delay calculation are real. Constructed errors and controlled randomness supply the cases; policy defaults remain unchanged.

Must Not Be Doubled

Retain the function, configuration or boundary guard under test and its assertions; replacing them removes the evidence.