Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MockedStreams.output shouldn't raise ExpectedOutputIsEmpty #6

Open
eliaslevy opened this issue Jan 9, 2017 · 1 comment
Open

MockedStreams.output shouldn't raise ExpectedOutputIsEmpty #6

eliaslevy opened this issue Jan 9, 2017 · 1 comment

Comments

@eliaslevy
Copy link

MockedStreams.output doesn't allow you to specify zero for the size of the expected output. That means you can't set an expectation that certain inputs should not have any outputs in your topology.

Instead of raising an exception when given a size of zero, output should verify that driver.readOutput returns null and return an empty set.

@spacer59
Copy link

maybe relevant but not defining output (even for terminating streams) does not materialize the stream, and as a result verifications fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants