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

[Enhancement] Send names of failed tests to Browserstack #2356

Closed
codekie opened this issue Mar 6, 2020 · 1 comment
Closed

[Enhancement] Send names of failed tests to Browserstack #2356

codekie opened this issue Mar 6, 2020 · 1 comment
Labels

Comments

@codekie
Copy link

codekie commented Mar 6, 2020

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Browserstack's session-update API supports a "failed" / "passed" status and a "reason" why the session has failed.

For the time being, Nightwatch's Browsertstack-"transport module" only sends a status and an empty string as reason.

Since the test-suites (which represent a session) may include numerous tests, it can be difficult to figure out which tests exactly failed. It would be helpful to send the name of the failed tests as "reason".

Describe how the solution will work
The "testSuiteFinished"-method (in lib/testsuite/index.js) has to pass the reporter-results to the testSuiteFinished-method of the Browserstack-"transport module", which then collects the names of the failed tests and passes them as "reason" to the Browserstack's session-update request.

Describe alternatives you've considered
I didn't find any.

Additional context
The "reason" to a failed Browserstack-session:
reason

@stale
Copy link

stale bot commented Jun 5, 2020

This issue has been automatically marked as stale because it has not had any recent activity.
If possible, please retry using the latest Nightwatch version and update the issue with any relevant details. If no further activity occurs, it will be closed. Thank you for your contribution.

@stale stale bot added the stale label Jun 5, 2020
@stale stale bot closed this as completed Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant