tech debt: Testing Fluvio Socket Multiplexor

[sehz]

Socket Multiplexor is quite complex with lots of different path and error condition. Existing integration test only cover a simple happy path. Need additional testing to cover different path. Maybe fuzzing testing?

[TanNgocDo]

There are several scenarios, to name a few:
Integration test:

1. Client have multiple multiplexer from one socket but one multiplexer is close(literal use:multiplexor_clone.terminate.notify(usize::MAX)); => should have some test case error handling for other multiplexers
2. Server dies after sometimes, client needs to have some test to handle.
   ......
   With fuzz test: maybe generating a variable of input msg for EchoRequest and AsyncRequest...

Just my 2-cent thinking, should be more scenarios
Thanks

[TanNgocDo]

@sehz , I have just 2 more naive test for multiplexing(not including fuzz yet)
Welcome for suggestions on more scenarios + refactoring code.
Thanks

[sehz]

Thanks. Will have someone look at that