ponyc
ponyc copied to clipboard
TCPExpect testing coverage gap
I am making changes in the Sendence version of TCPExpect to try out some possible performance improvements and noticed a gap in the test coverage for TCPExpect.
We don't verify after expect has been set to a non zero value and we read some data that setting it to 0 will result in all remaining data being read.