flutter-bloc-testing

Testing concurrency transformers in Bloc requires controlling async timing with Completer. This proves behavioral contracts for restartable, droppable, or sequential handlers by verifying cancellation of in-flight work during event processing.

Yes, you can mock repository calls in Flutter Bloc tests without code generation by using mocktail. You must register fallback values for complex argument types and use argument matching to stub repository calls for controlled test environments.

When testing HydratedBloc persistence, use an in-memory Storage fake to replace HydratedBloc.storage. Clearing this fake storage per test ensures isolated, deterministic rehydration round-trip verification after a simulated restart.

The best way to verify a Bloc concurrency transformer contract is using controlled timing with Completer. This verifies behavioral contracts for restartable, droppable, or sequential handlers by proving the cancellation of in-flight work.

Bloc tests fail when asserting async event handler states if you don't control async timing. You must use controlled timing with Completer and ordered stream expectations to verify the deterministic emitted state sequence for driven events.