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

Generate a new rerun.sh file after running the original #25

Open
Nicolas-Moore opened this issue Jul 24, 2021 · 4 comments · May be fixed by #68
Open

Generate a new rerun.sh file after running the original #25

Nicolas-Moore opened this issue Jul 24, 2021 · 4 comments · May be fixed by #68
Assignees
Labels
enhancement New feature or request

Comments

@Nicolas-Moore
Copy link

Nicolas-Moore commented Jul 24, 2021

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.

@mikesalvia mikesalvia added the enhancement New feature or request label Aug 4, 2021
@mikesalvia
Copy link
Collaborator

@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.

@mikesalvia mikesalvia added documentation Improvements or additions to documentation and removed unit tests enhancement New feature or request labels Apr 19, 2022
@jansmitmans
Copy link
Contributor

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?
If no, would you be open to someone (as in: me) contributing this feature?

Cheers,
Jan

@jansmitmans
Copy link
Contributor

I have worked on a feature to enable this.
Please check this PR at your own convenience.
As I am new to this kind of contribution, I am not sure if this is the way to go - give me a slap on the wrist if something is not as expected for you.

@jansmitmans jansmitmans linked a pull request Aug 12, 2023 that will close this issue
@mikesalvia mikesalvia added enhancement New feature or request and removed documentation Improvements or additions to documentation labels Sep 3, 2023
@mikesalvia
Copy link
Collaborator

@corny1989 Thank you for your contributions and your help working to deliver the PR to allow for this.

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

Successfully merging a pull request may close this issue.

4 participants