Github user mbalassi commented on the pull request:
https://github.com/apache/flink/pull/789#issuecomment-109218281
Both are good points.
As for the socket test I can do one of the following:
* Do not test it
* Test it with smaller data
* Mock the socket with some collection
I am not not really happy with any of these options to be honest, but maybe
I am just missing something.
As for the ITCases, you are right, I have to admit that I was looking at
the
[AvroOutputFormatTest](https://github.com/apache/flink/blob/master/flink-staging/flink-avro/src/test/java/org/apache/flink/api/avro/AvroOutputFormatTest.java)
and named my tests accordingly. So you would suggest renaming that too then?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
