11# =============================
22# Set BrowserStack Credentials
33# =============================
4- # Add your BrowserStack userName and acccessKey here or set BROWSERSTACK_USERNAME and
4+ # Add your BrowserStack userName and accessKey here or set BROWSERSTACK_USERNAME and
55# BROWSERSTACK_ACCESS_KEY as env variables
66userName : YOUR_USERNAME
77accessKey : YOUR_ACCESS_KEY
88
99# ======================
10- # Organizing your tests
10+ # BrowserStack Reporting
1111# ======================
12- # Use `projectName`, `buildName`, `name` capabilities to organise your tests
13- # `name` is the name of your test sessions and is automatically picked from your
14- # test name and doesn't need to be set manually when using BrowserStack SDK
15- # `buildName` is used to name your CI/CD job or the execution of your test suite.
16- # Ensure you add a dynamic identifier, like an incremental build number from your
17- # CI/CD or timestamp at the end of every build; otherwise tests from different
18- # executions will be grouped together on BrowserStack
19- buildName : browserstack-build-1
20- # Use `projectName` to set the name of your project. Example, Marketing Website
21- projectName : BrowserStack Samples
22- # Use `framework` to set the framework of your project. Example, testng, cucumber, cucumber-testng
12+ # The following capabilities are used to set up reporting on BrowserStack:
13+ # Set 'projectName' to the name of your project. Example, Marketing Website
14+ projectName : BrowserStack Samples
15+ # Set `buildName` as the name of the job / testsuite being run
16+ buildName : browserstack build
17+ # `buildIdentifier` is a unique id to differentiate every execution that gets appended to
18+ # buildName. Choose your buildIdentifier format from the available expressions:
19+ # ${BUILD_NUMBER} (Default): Generates an incremental counter with every execution
20+ # ${DATE_TIME}: Generates a Timestamp with every execution. Eg. 05-Nov-19:30
21+ # Read more about buildIdentifiers here -> https://www.browserstack.com/docs/automate/selenium/organize-tests
22+ buildIdentifier : ' #${BUILD_NUMBER}' # Supports strings along with either/both ${expression}
23+ # Set `framework` of your test suite. Example, `testng`, `cucumber`, `cucumber-testng`
24+ # This property is needed to send test context to BrowserStack (test name, status)
2325framework : testng
2426
2527# =======================================
@@ -36,10 +38,10 @@ platforms:
3638 osVersion : 10
3739 browserName : Edge
3840 browserVersion : latest
39- - device : Samsung Galaxy S22 Ultra
41+ - deviceName : Samsung Galaxy S22 Ultra
4042 browserName : chrome # Try 'samsung' for Samsung browser
4143 osVersion : 12.0
42-
44+
4345# =======================
4446# Parallels per Platform
4547# =======================
@@ -60,12 +62,13 @@ source: testng:sample-master:v1.1
6062# Set browserStackLocal to true if your website under test is not accessible publicly over the internet
6163# Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction
6264browserstackLocal : true # <boolean> (Default false)
63- # browserStackLocalOptions:
64- # Options to be passed to BrowserStack local in-case of advanced configurations
65- # localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local.
66- # forceLocal: true # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel.
67- # Entire list of arguments available here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections
6865
66+ # Options to be passed to BrowserStack local in-case of advanced configurations
67+ # browserStackLocalOptions:
68+ # localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local.
69+ # forceLocal: true # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel.
70+ # Entire list of arguments available here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections
71+
6972# ===================
7073# Debugging features
7174# ===================
0 commit comments