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

All the tests will re-run even if a single test failed #87

Open
rakeshnambiar opened this issue Dec 26, 2020 · 6 comments
Open

All the tests will re-run even if a single test failed #87

rakeshnambiar opened this issue Dec 26, 2020 · 6 comments

Comments

@rakeshnambiar
Copy link

All the tests will re-run even if a single test failed. I am using serenity-js framework [chai assertions].

Configuration:

    onCleanUp: function (results) {
        retry.onCleanUp(results);
    },
    onPrepare: function () {
        retry.onPrepare();
    },
    afterLaunch: function() {
        return retry.afterLaunch(1);
    }
@rakeshnambiar
Copy link
Author

@jan-molak any thoughts?

@rakeshnambiar
Copy link
Author

@dreuxl @amrot17 Please take a look at this issue.

@jan-molak
Copy link

@rakeshnambiar if you're using Serenity/JS with the Mocha adapter, you can tell Mocha to retry the failed tests, therefore removing the need for protractor-retry.

I'll be adding support for retrying failed Cucumber tests soon.

@dreuxl
Copy link
Contributor

dreuxl commented Jan 5, 2021

@rakeshnambiar are u running your suite in parallel , let s say using sauce labs?
https://github.com/yahoo/protractor-retry#known-caveat
If not it s expected.

Also note, the mocha retry may address your issue, even though the mechanism is different:

  • mocha is retrying on the fly (same browser/session)
  • protractor-retry is retrying at the end of a suite and create a new session (clean environment) for the retry

@rakeshnambiar
Copy link
Author

@dreuxl no, the execution in the sequential order on selenium-grid. I am not using the Mocha runner and it's a cucumber test by using serenity-js framework. Probably like @jan-molak mentioned, I will have to wait.

@idem7x
Copy link

idem7x commented Feb 19, 2021

I think this could happen if you have your specs inside capabilities. Moving it outside capabilities will solve issue.

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

4 participants