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
[🐛 Bug]: BrowserStack build identifier is not set when BROWSERSTACK_BUILD_NAME environment variable is set #12674
Comments
It seems like you are also setting the |
I think I have tried all combinations already. But checked them again. When environment variables are set then adding But when I remove environment variables and hardcode build name in configuration, then setting |
@kwiniarski can you provide a minimal reproducible example? |
I can't post the repo where I have this, but I will try to extract the minimal code. I think it will be helpful because I also have another potential bug with BrowserStack there. |
I have created repository with simple example that reproduces described issue: https://github.com/kwiniarski/wdio-browserstack-stencil. |
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
8.35.1
Node.js Version
v20.9.0
Mode
Standalone Mode
Which capabilities are you using?
What happened?
I'm using WebdriverIO with BrowserStack service and I have noticed that when I set build name through BROWSERSTACK_BUILD_NAME environment variable, then setting build identifier has no effect. Digging a little into the code I have found this condition in launcher.ts which effectively terminates processing of build identifier when BROWSERSTACK_BUILD_NAME is set.
webdriverio/packages/wdio-browserstack-service/src/launcher.ts
Lines 701 to 705 in fa5f02f
What is your expected behavior?
No response
How to reproduce the bug.
Just set up
BROWSERSTACK_BUILD_NAME
variable and then run tests using browserstack-service. In BrowserStack dashboard you will see that following build are not numbered. All test sessions are appended to the one, already existing build.Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: