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
--retires does not seems to work #213
Comments
Hi @kinyat! Thanks for reporting it! Can you provide some help with fixing it? I am busy with my university thesis |
+1, as the nature of E2E tests is a certain instability :) |
This issue is depends on CucumberJS issue: cucumber/cucumber-js#727 |
Currently closing it. Please reopen if the Cucumber issue is resolved |
hi @mucsi96 , Development at cucumber JS is almost completed. When is the next release planned for us? Link to PR at cucumberJS--> cucumber/cucumber-js#1114 |
There's no release planned. But I can increase the peer dependency range if it still work with latest cucumberjs and do a release. This package is deprecated and not actively maintained. You should start about thinking about migrating away from it. I suggest checking nightwatch-api |
I'm submitting a ... (check one with "x")
Current behavior
It is currently just ignoring the --retries option
Expected/desired behavior
It should retry for a certain number of times depending on the option value
Reproduction of the problem
node ./node_modules/.bin/nightwatch --retries 3
What is the expected behavior?
It should retry 3 times
What is the motivation / use case for changing the behavior?
Because tests are not reliable, sometimes we need to rerun a few times to make sure it is not a false alarm
Please tell us about your environment:
nightwatch-cucumber version:
7.1.0
nightwatch version:
0.9.14
cucumber version:
2.0.0-rc.5
Node.js version:
6.10
The text was updated successfully, but these errors were encountered: