Test Terry
“Add ten seconds; CI has time.”
Can retries and awaits be tested before lunch?
Elevator answer
Advance a controllable clock, complete the Await with its correlation ID, and assert the durable transition. Sleeping 30 seconds is not testing time; it is donating life to CI.
3 coffee-machine misconceptions
Async Andy
“Flaky tests prove concurrency is real.”
Workflow Wendy
“A timer is a business process.”
The real explanation
Wall-clock tests are tiny weather forecasts. For a durable Await, admit the work, capture its correlation, advance a controllable clock, submit the completion twice, and inspect the resume or timeout transition. For retry, control the attempt sequence and terminal result. The test should move time; time should not move the test suite toward retirement.
This is more than convenience. A test that waits rarely proves which transition occurred; it merely proves that something eventually happened in one environment. Deterministic tests can assert that a duplicate completion is rejected, a timeout routes to the correct state, or a retry preserves its idempotency key.
TPF’s execution model supplies the semantic hooks; teams still need to write the cases that matter to their business promise.
Trade-offs
TPF gains deterministic temporal tests. It gives up casual sleeps and vague asynchronous assertions.
When TPF is not a good fit
If a team cannot control or observe time and completion in tests, first improve the boundary design.