Order 360's payment actions

Verification Boundary

The component suite renders the named screen with controlled adapter results.

What This Suite Proves

The registered cases check order 360's payment actions with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

Real Dependencies and Test Doubles

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.