How to mock EventChannel in unit test? #38954

Activity

1. befovy

   changed the title [-]How to mock EventChannel ?[/-] [+]How to mock EventChannel in unit test?[/+] on Aug 21, 2019
2. juliocbcotta commented on Aug 21, 2019

   

   juliocbcotta

   on Aug 21, 2019

   More actions

   Not a great solution, but still a solution. here
   EventChannel is backed using a MethodChannel... so do not worry about the link above creating a MethodChannel.

   Flutter could have something similar to MethodChannel. setMockMethodCallHandler.

   👍React with 👍1Reacted by 于飞白
3. befovy commented on Aug 21, 2019

   

   befovy

   on Aug 21, 2019

   Author

   More actions

   @BugsBunnyBR 👍 Your answer has resolved my problems. Thanks.

   I known EventChannel is backed using a MethodChannel.

   class EventChannel {
     Stream<dynamic> receiveBroadcastStream([ dynamic arguments ]) {
       final MethodChannel methodChannel = MethodChannel(name, codec);
       StreamController<dynamic> controller;
       controller = StreamController<dynamic>.broadcast(onListen: () async {
         defaultBinaryMessenger.setMessageHandler(name, (ByteData reply) async {
           if (reply == null) {
             controller.close();
           } else {
             try {
               controller.add(codec.decodeEnvelope(reply));
             } on PlatformException catch (e) {
               controller.addError(e);
             }
           }
           return null;
         });
     ...
   }

   The event Stream comes from MessageHandler set in receiveBroadcastStream.
   I tried to send message by call defaultBinaryMessenger.send which is wrong.
   Actually, defaultBinaryMessenger.handlePlatformMessage is right.
4. befovy

   closed this as completedon Aug 21, 2019
5. github-actions commented on Aug 28, 2021

   

   github-actionsbot

   on Aug 28, 2021

   More actions

   This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
6. github-actions

   locked as resolved and limited conversation to collaborators on Aug 28, 2021