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

[Christopher] FIX: If background fails, rerun just runs the first scenario and skips other scenarios #650

Closed
wants to merge 1 commit into from

Conversation

christopher-rex
Copy link

On a feature execution, if the background fails, the rerun.txt file records the feature along with the line number of first scenario. Consequently during rerun only this scenario runs and all other scenarios in the feature file are ignored.

The fix is to capture just the feature file name WITHOUT any line numbers in rerun.txt if background fails. This results in rerunning the entire feature file with all scenarios.

…ded in rerun.txt without the line number of the scenario. This results in rerunning the entire feature file during rerun instead of executing just the first scenario and skipping all other scenarios.
@tooky
Copy link
Member

tooky commented Mar 12, 2014

Thanks for taking a look at this @christopher-rex.

It's probably safest to fix this in the v1.3.x-bugfix branch right now - especially if you want it to be released soon. The master branch is targeting cucumber 2.0 and is not likely to be released soon.

If you could write a spec or scenario that demonstrates this behaviour that would also be really useful, to ensure we don't get a regression in future versions.

@mattwynne
Copy link
Member

@christopher-rex would an acceptable solution be to record all of the scenarios in the feature in the rerun formatter output? That approach seems much more compatible with Cucumber 2.0's design.

@mattwynne
Copy link
Member

Closing due to inactivity.

@mattwynne mattwynne closed this Dec 22, 2014
@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.

3 participants