Open vweevers opened 6 years ago
I think it does. Definitely something it's worth having, and including it in the docs as well.
My only question is.. how much of this could be generic, and not tied to a stream? We cannot really verify that the data is correct, so we should focus on signal ordering, etc.
The inconsistency also exists in Core (OutgoingMessage
for example), so it might be very good to have this test suite available.
I think an "abstract test suite" for streams (akin to
abstract-leveldown
) would be great to have because:readable-stream
but this is not enough of a guarantee that it behaves the same. For example, many modules have implemented their own non-underscoreddestroy()
with inconsistent semantics as well as their owndestroyed
state tracking. Merely updating the version ofreadable-stream
won't fix that and an upgrade guide does not exist.fs
, or at least to identify differencespump/pipeline
andend-of-stream/finished
.@mcollina @mafintosh I would love to hear your thoughts if you have time.