You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: browserstack.yml
+27-22Lines changed: 27 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -3,24 +3,26 @@
3
3
# =============================
4
4
# Add your BrowserStack userName and accessKey here or set BROWSERSTACK_USERNAME and
5
5
# BROWSERSTACK_ACCESS_KEY as env variables
6
-
userName: BROWSERSTACK_USERNAME
7
-
accessKey: BROWSERSTACK_ACCESS_KEY
8
-
9
-
framework: selenide-testng
6
+
userName: YOUR_USERNAME
7
+
accessKey: YOUR_ACCESS_KEY
10
8
11
9
# ======================
12
-
#Organizing your tests
10
+
#BrowserStack Reporting
13
11
# ======================
14
-
# Use `projectName`, `buildName`, `name` capabilities to organise your tests
15
-
# `name` is the name of your test sessions and is automatically picked from your
16
-
# test name and doesn't need to be set manually when using BrowserStack SDK
17
-
# `buildName` is used to name your CI/CD job or the execution of your test suite.
18
-
# Ensure you add a dynamic identifier, like an incremental build number from your
19
-
# CI/CD or timestamp at the end of every build; otherwise tests from different
20
-
# executions will be grouped together on BrowserStack
21
-
buildName: browserstack-build-1
22
-
# Use `projectName` to set the name of your project. Example, Marketing Website
23
-
projectName: BrowserStack Samples
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)
25
+
framework: selenide-testng
24
26
25
27
# =======================================
26
28
# Platforms (Browsers / Devices to test)
@@ -36,10 +38,10 @@ platforms:
36
38
osVersion: 10
37
39
browserName: Edge
38
40
browserVersion: latest
39
-
- device: Samsung Galaxy S22 Ultra
41
+
- deviceName: Samsung Galaxy S22 Ultra
40
42
browserName: chrome # Try 'samsung' for Samsung browser
41
43
osVersion: 12.0
42
-
44
+
43
45
# =======================
44
46
# Parallels per Platform
45
47
# =======================
@@ -51,19 +53,22 @@ platforms:
51
53
# Example 2 - If you have configured 1 platform and set `parallelsPerPlatform` as 5, a total of 5 (1 * 5) parallel threads will be used on BrowserStack
52
54
parallelsPerPlatform: 1
53
55
56
+
source: selenide:sample-master:v1.3
57
+
54
58
# ==========================================
55
59
# BrowserStack Local
56
60
# (For localhost, staging/private websites)
57
61
# ==========================================
58
62
# Set browserStackLocal to true if your website under test is not accessible publicly over the internet
59
63
# Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction
0 commit comments