Which testing scenario does not work with test clocks in Stripe?

Test clocks in Stripe are designed to facilitate the testing of time-dependent features, allowing developers to simulate how their applications will behave over time without waiting for actual passage of time. They are particularly useful for scenarios where subscription billing or time-triggered events are involved.

Simulating time-based subscriptions allows developers to manipulate time effectively, testing how subscriptions behave as they start, renew, or expire. Invoicing at specific intervals also benefits from test clocks, enabling developers to generate invoices at set times according to the subscription schedule created with the test clock.

However, ensuring that the integration processes account for webhooks involves verifying that your application correctly receives and processes real-time events from Stripe. This does not rely on time manipulation but rather on the correct handling of events as they occur. Webhook testing typically uses mock events or live events rather than test clocks, as the focus is on validating the response and processing of those events in the application.

Testing refund processes, while it can be time-dependent in some cases, can still be validated effectively in a separate manner. Therefore, the limitation lies in the nature of webhooks that do not directly incorporate time manipulations offered by test clocks, making it a scenario that does not function with them effectively.