workflow-integration-testing

Use renderForTest to run your workflow with a real runtime, then drive WorkflowTurbine to consume and validate renders, outputs, and snapshots during tests.

Unlike unit tests using testRender, renderForTest executes a real workflow runtime that runs real child workflows, real workers, and real async behavior for true end-to-end integration testing.

Validate end-to-end workflow renders, events, and outputs by driving WorkflowTurbine to consume each rendering and output snapshot produced by the real runtime during integration testing.

Yes, testing multi-step user flows requires a real runtime to execute real workers and async behavior, ensuring deterministic lifecycle management and proper cleanup across all steps.

Yes, WorkflowTurbine consumes renders, outputs, and snapshots during tests, allowing you to validate end-to-end asynchronous behavior and deterministic lifecycle management for Kotlin workflows.

Use end-to-end integration testing when you need to validate real workers, real child workflows, and async behavior across multi-step user flows, rather than isolated render states in unit tests.