|
| 1 | +# ============================= |
| 2 | +# Set BrowserStack Credentials |
| 3 | +# ============================= |
| 4 | +# In the terminal export BROWSERSTACK_USERNAME=<secret> |
| 5 | +# In the terminal export BROWSERSTACK_ACCESS_KEY=<secret> |
| 6 | + |
| 7 | +# ====================== |
| 8 | +# BrowserStack Reporting |
| 9 | +# ====================== |
| 10 | +# The following capabilities are used to set up reporting on BrowserStack: |
| 11 | +# Set 'projectName' to the name of your project. Example, Marketing Website |
| 12 | +projectName: Thunderbird Accounts |
| 13 | +# Set `buildName` as the name of the job / testsuite being run |
| 14 | +buildName: TB Accounts E2E Tests |
| 15 | +# `buildIdentifier` is a unique id to differentiate every execution that gets appended to |
| 16 | +# buildName. Choose your buildIdentifier format from the available expressions: |
| 17 | +# ${BUILD_NUMBER} (Default): Generates an incremental counter with every execution |
| 18 | +# ${DATE_TIME}: Generates a Timestamp with every execution. Eg. 05-Nov-19:30 |
| 19 | +# Read more about buildIdentifiers here -> https://www.browserstack.com/docs/automate/selenium/organize-tests |
| 20 | +buildIdentifier: '${DATE_TIME}' |
| 21 | + |
| 22 | +# ======================================= |
| 23 | +# Platforms (Browsers / Devices to test) |
| 24 | +# ======================================= |
| 25 | +# Platforms object contains all the browser / device combinations you want to test on. |
| 26 | +# Entire list available here -> (https://www.browserstack.com/list-of-browsers-and-platforms/automate) |
| 27 | +platforms: |
| 28 | + - os: OS X |
| 29 | + osVersion: Sequoia |
| 30 | + browserName: playwright-firefox |
| 31 | + browserVersion: latest |
| 32 | + playwrightConfigOptions: |
| 33 | + name: Firefox-OSX |
| 34 | + setup: |
| 35 | + - name: 'setup_firefox_auth' |
| 36 | + testMatch: 'auth.desktop.setup.ts' |
| 37 | + use: |
| 38 | + storageState: 'test-results/.auth/user.json' |
| 39 | + |
| 40 | +# ======================= |
| 41 | +# Parallels per Platform |
| 42 | +# ======================= |
| 43 | +# The number of parallel threads to be used for each platform set. |
| 44 | +# BrowserStack's SDK runner will select the best strategy based on the configured value |
| 45 | +# |
| 46 | +# Example 1 - If you have configured 3 platforms and set `parallelsPerPlatform` as 2, a total of 6 (2 * 3) parallel threads will be used on BrowserStack |
| 47 | +# |
| 48 | +# 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 |
| 49 | +parallelsPerPlatform: 1 |
| 50 | + |
| 51 | +# ========================================== |
| 52 | +# BrowserStack Local |
| 53 | +# (For localhost, staging/private websites) |
| 54 | +# ========================================== |
| 55 | +# Set browserStackLocal to true if your website under test is not accessible publicly over the internet |
| 56 | +# Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction |
| 57 | +browserstackLocal: false # <boolean> (Default false) |
| 58 | +# browserStackLocalOptions: |
| 59 | +# Options to be passed to BrowserStack local in-case of advanced configurations |
| 60 | + # localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local. |
| 61 | + # forceLocal: true # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel. |
| 62 | + # Entire list of arguments available here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections |
| 63 | + |
| 64 | +# =================== |
| 65 | +# Debugging features |
| 66 | +# =================== |
| 67 | +debug: false # <boolean> # Set to true if you need screenshots for every selenium command ran |
| 68 | +networkLogs: false # <boolean> Set to true to enable HAR logs capturing; off as may contain sensitive info like login API requests |
| 69 | +consoleLogs: info # <string> Remote browser's console debug levels to be printed (`disable`, `errors`, `warnings`, `info`, or `verbose`) |
| 70 | +framework: playwright |
| 71 | +browserstack.playwrightVersion: 1.55.0 # must match our client playwright version in package.json; this is the latest supported in BrowserStack |
| 72 | +browserstack.playwrightLogs: false # disable playwright logs appearing on browserstack builds as may contain sensitive info like credentials |
| 73 | +# CUSTOM_TAG_<INT>: # <string> (Default: parent folder name of the test file) Custom tag for your test suite |
| 74 | +browserstack.maskBasicAuth: true # mask username and passwords from browserstack session logs |
| 75 | +browserstack.maskCommands: sendType, sendPress, setHTTPCredentials, setStorageState, setWebAuthnCredentials # prevent sensitive info appearing in browserstack session logs |
| 76 | +# Test Observability is an intelligent test reporting & debugging product. It collects data using the SDK. Read more about what data is collected at https://www.browserstack.com/docs/test-observability/references/terms-and-conditions |
| 77 | +# Visit observability.browserstack.com to see your test reports and insights. To disable test observability, specify `testObservability: false` in the key below. |
| 78 | +testObservability: false |
0 commit comments