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

Retried tests on BrowserStack are left unmarked #3746

Closed
MicahLC opened this issue May 23, 2023 · 0 comments · Fixed by #3764
Closed

Retried tests on BrowserStack are left unmarked #3746

MicahLC opened this issue May 23, 2023 · 0 comments · Fixed by #3764
Assignees
Labels
bug cloud-providers Issues related to running tests with cloud providers (AWS, Browserstack, Saucelabs, etc)

Comments

@MicahLC
Copy link
Contributor

MicahLC commented May 23, 2023

Description of the bug/issue

When I run tests on BrowserStack with retries, I expect that retried tests will be marked as failed, but instead they are left as unmarked.

Steps to reproduce

  1. Have a test that will fail.
  2. Run it on BrowserStack with --suiteRetries 2 or more than 2.
  3. All runs in BrowserStack produced by that test should be marked as failed, but all except the last are left unmarked.

Sample test

Any basic test that fails will work to repro the issue.

Command to run

nightwatch test/sampleTest.js --suiteRetries 2

Verbose Output

No response

Nightwatch Configuration

No response

Nightwatch.js Version

3.0.0-beta-1 (also happens with 2.6.21 and 2.6.16)

Node Version

16.20.0

Browser

Any

Operating System

Any

Additional Information

Screen Shot 2023-05-23 at 11 47 14 AM
@gravityvi gravityvi added bug cloud-providers Issues related to running tests with cloud providers (AWS, Browserstack, Saucelabs, etc) labels May 24, 2023
@gravityvi gravityvi self-assigned this Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cloud-providers Issues related to running tests with cloud providers (AWS, Browserstack, Saucelabs, etc)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants