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

Make the Rerun Formatter consistent with the exit code #860

Merged
merged 2 commits into from
Jun 19, 2015

Conversation

brasmusson
Copy link
Contributor

I think the invariant for the behaviour of the Rerun Formatter should be:
When the exit code is zero => the Rerun formatter output is empty
When the exit code is non-zero => the Rerun formatter output is not empty

This PR changes the behaviour the Rerun Formatter to fulfil this invariant.

The final change (fc356b1) requires cucumber/cucumber-ruby-core#92.

The exit code is zero => the Rerun formatter output is empty
The exit code is non-zero => the Rerun formatter output is not empty
@mattwynne
Copy link
Member

This is going to need a little update to work since I tweaked the method name in cucumber/cucumber-ruby-core#92

@brasmusson brasmusson force-pushed the rerun-formatter-exit-code branch from dbdc338 to fc356b1 Compare June 11, 2015 16:03
@brasmusson
Copy link
Contributor Author

So, it was easy enough to tweak the name used here too.

@mattwynne mattwynne modified the milestone: 2.0 Jun 19, 2015
mattwynne added a commit that referenced this pull request Jun 19, 2015
Make the Rerun Formatter consistent with the exit code
@mattwynne mattwynne merged commit 94767a7 into master Jun 19, 2015
@brasmusson brasmusson deleted the rerun-formatter-exit-code branch June 20, 2015 06:18
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants