Open seriema opened 8 years ago
The DigDug docs mention:
buildId | number | The build number of the software being tested by the job. Supported by Sauce Labs. https://theintern.github.io/digdug/global.html
The BrowserStack docs mention:
build | Allows the user to specify a name for a logical group of tests. | Example: build 4.5 | Default: Untitled Build https://www.browserstack.com/automate/capabilities#capabilities-browserstack
It'd be pretty nifty with support for buildId on BrowserStack. I hacked it into the environments config just to try it out, and it looks pretty good:
buildId
The config I used:
{ browserName: "chrome", os: "WINDOWS", os_version: "10", name: "example session name", build: 3186 }
At least SauceLabs, BrowserStack, and CrossBrowserTesting support some level of test description;
build
name
project
tags
The DigDug docs mention:
The BrowserStack docs mention:
It'd be pretty nifty with support for
buildId
on BrowserStack. I hacked it into the environments config just to try it out, and it looks pretty good:The config I used: