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

Show all links to all cloud test sessions in concurrency mode #4346

Closed
aleks-pro opened this issue Oct 2, 2019 · 2 comments
Closed

Show all links to all cloud test sessions in concurrency mode #4346

aleks-pro opened this issue Oct 2, 2019 · 2 comments
Assignees
Labels
FREQUENCY: level 2 TYPE: enhancement The accepted proposal for future implementation.

Comments

@aleks-pro
Copy link
Collaborator

Run multiple tests in concurrency mode on BrowserStack. A resulting report will contain the same link for every failed test. Even if tests were failed in different sessions.
You can use the attached example project to reproduce the issue.
Command: testcafe -c 4 "browserstack:Chrome" "./tests/*.js" -r xunit:res.xml
examples.zip

  • testcafe version: 1.5.0
@aleks-pro aleks-pro added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 2, 2019
@AndreyBelym AndreyBelym added FREQUENCY: level 1 TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: bug The described behavior is considered as wrong (bug). labels Sep 22, 2021
@AndreyBelym AndreyBelym changed the title TestCafe cannot recognize in which session test failed in concurrency mode Show links to all cloud test sessions in concurrency mode Apr 20, 2022
@AndreyBelym
Copy link
Contributor

The same for SauceLabs: DevExpress/testcafe-browser-provider-saucelabs#78.

@github-actions
Copy link

github-actions bot commented Jul 8, 2022

Release v1.20.0-rc.1 addresses this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FREQUENCY: level 2 TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

3 participants