-
Notifications
You must be signed in to change notification settings - Fork 13
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
Generate a new rerun.sh file after running the original #25
Comments
@Nicolas-Moore this technically can be achieved by enabling the service and writing reports to different locations. This definitely can use a unit test though. |
Hey Mike, I do not understand how this would be possible to be honest. Wouldn't you always need to remove the DISABLE_RERUN env from the generated .sh as well, in addition to using different report directories? Are there any plans from your side to make this a configurable feature? Cheers, |
I have worked on a feature to enable this. |
@corny1989 Thank you for your contributions and your help working to deliver the PR to allow for this. |
Hello, I just started using this package today and it is very useful. I have one question though, is there a way to generate a new rerun.sh file after running the original rerun.sh file?
For example say you run a set of feature files and a few scenarios fail and are added to the rerun.sh file. You now run the generated rerun.sh file and one of the scenarios fails again. Is there a way to generate a new rerun.sh file that only contains the one failing scenario?
I tried to do this by manually editing the originally generated rerun.sh file and changing the env variable DISABLE_RERUN to false but that did not work.
The text was updated successfully, but these errors were encountered: