Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Read and save failed features if
#run_all
fails. Here's the workflow I'm going for:From what I can tell, there's no way to tell guard-cucumber to rerun the saved failed features without calling
#run_on_change
. Here's my Guardfile:It's cheating, but I'm passing non-feature filenames to guard-cucumber which it's smart enough to ignore. The end result is when an app file is saved, the failed features are rerun.
I've only started using guard yesterday so please let me know if I'm missing something obvious. I wouldn't be surprised. In the mean time, I'm going to give this patch a try today and see how it feels.