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

Using rerun of failed tests with @rerun.txt #89

Closed
Boxdove opened this issue Jul 27, 2017 · 6 comments
Closed

Using rerun of failed tests with @rerun.txt #89

Boxdove opened this issue Jul 27, 2017 · 6 comments

Comments

@Boxdove
Copy link

Boxdove commented Jul 27, 2017

Hi, could you please help me how to use in appropriate way this feature.
I use cucumber 1.3.3, protractor-cuumber-framework 2.0.0

At present I have format: ['pretty', 'rerun:@rerun.txt'] in config.js, it creates @rerun.text file with failed scenarios
but have no idea how to run this file again
If I create separate Rerun formatter feature, @rerun.txt file might be run after all features...
What did I miss?

Thank you

@darrinholst
Copy link
Contributor

You need to pass in the rerun argument with the file as the value. An example is here

@darrinholst
Copy link
Contributor

you'll also need to be using at least version 2.2.0

@darrinholst
Copy link
Contributor

let us know if it doesn't work

@Boxdove
Copy link
Author

Boxdove commented Aug 3, 2017

Sorry for late replay.
Thanks a lot, that's all I needed)

@kieranbop
Copy link

kieranbop commented Oct 12, 2017

The example doesn't show how we use protractor cucumber to create that @rerun file @darrinholst . When I append the various options after it will just hang and not write the failing scenarios to the file. How can I set it to create a file on the initial run and then I can re run it after with the example above

@darrinholst
Copy link
Contributor

you have to run it the first time with a rerun formatter - --format rerun:@rerun.txt

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

No branches or pull requests

3 participants