In my experience doing Pigeon conversions of our plugins, dartHostTestHandler didn't make tests noticeably easier than simply mocking/faking/stubbing the host API class directly, and in some cases it was actually harder to use correctly to simulate things like exceptions. We have a robust test suite for Pigeon itself, so having package-level unit tests covering part of the Pigeon serialization isn't necessary, and the test generator is another generator we need to maintain.

We should try to eliminate all use of dartHostTestHandler in our own plugins, and if we are able to do so without any significant issues, remove the test generator from Pigeon entirely to reduce complexity and ongoing maintenance costs.

Current usage:

• camera_android_camerax
• file_selector_ios
• file_selector_linux
• file_selector_macos
• file_selector_windows
• image_picker_android
• image_picker_ios
• in_app_purchase_storekit
• path_provider_android
• path_provider_foundation
• shared_preferences_android
• shared_preferences_foundation
• url_launcher_windows
• video_player_android
• video_player_avfoundation
• webview_flutter_wkwebview