asyncredux-navigation

You test navigation by dispatching NavigateAction via AsyncRedux to trigger push, pop, and replace operations on named routes. This decouples navigation testing from the widget tree, allowing route transitions to be verified in isolation.

Controlling navigation with AsyncRedux involves registering a navigator key via NavigateAction.setNavigatorKey and binding it to MaterialApp. You then dispatch pushNamed or popUntil actions within Redux actions to manage route changes after async operations.

To set up NavigateAction, call NavigateAction.setNavigatorKey(...) at startup and configure your MaterialApp with the same navigatorKey. This enables dispatched push, pop, and remove actions to drive testable route transitions across named routes.

Yes, you can navigate after an async operation by including a NavigateAction, such as pushReplacement or pushNamed, within your AsyncRedux action. This dispatches the route change automatically once the async process finishes.

Yes, NavigateAction supports dispatching replace and remove actions to modify the navigation stack. It also handles push, pushNamed, pop, and popUntil, providing comprehensive control over named route transitions during testing.