|
| 1 | +# ============================= |
| 2 | +# Set BrowserStack Credentials |
| 3 | +# ============================= |
| 4 | +# Add your BrowserStack userName and acccessKey here or set BROWSERSTACK_USERNAME and |
| 5 | +# BROWSERSTACK_ACCESS_KEY as env variables |
| 6 | +userName: YOUR_USERNAME |
| 7 | +accessKey: YOUR_ACCESS_KEY |
| 8 | + |
| 9 | +# ====================== |
| 10 | +# Organizing your tests |
| 11 | +# ====================== |
| 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 | + |
| 23 | +# ======================================= |
| 24 | +# Platforms (Browsers / Devices to test) |
| 25 | +# ======================================= |
| 26 | +# Platforms object contains all the browser / device combinations you want to test on. |
| 27 | +# Entire list available here -> (https://www.browserstack.com/list-of-browsers-and-platforms/automate) |
| 28 | +platforms: |
| 29 | + - os: OS X |
| 30 | + osVersion: Big Sur |
| 31 | + browser: Chrome |
| 32 | + browserVersion: latest |
| 33 | + - os: Windows |
| 34 | + osVersion: 10 |
| 35 | + browser: Edge |
| 36 | + browserVersion: latest |
| 37 | + - device: Samsung Galaxy S22 Ultra |
| 38 | + browserName: chrome # Try 'samsung' for Samsung browser |
| 39 | + osVersion: 12.0 |
| 40 | + |
| 41 | +# ========================================== |
| 42 | +# BrowserStack Local |
| 43 | +# (For localhost, staging/private websites) |
| 44 | +# ========================================== |
| 45 | +# Set browserStackLocal to true if your website under test is not accessible publicly over the internet |
| 46 | +# Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction |
| 47 | +browserstackLocal: true # <boolean> (Default false) |
| 48 | +# browserStackLocalOptions: |
| 49 | +# Options to be passed to BrowserStack local in-case of advanced configurations |
| 50 | + # localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local. |
| 51 | + # forceLocal: true # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel. |
| 52 | + # Entire list of arguments availabe here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections |
| 53 | + |
| 54 | +# =================== |
| 55 | +# Debugging features |
| 56 | +# =================== |
| 57 | +debug: false # <boolean> # Set to true if you need screenshots for every selenium command ran |
| 58 | +networkLogs: false # <boolean> Set to true to enable HAR logs capturing |
| 59 | +consoleLogs: errors # <string> Remote browser's console debug levels to be printed (Available levels: `disable`, `errors`, `warnings`, `info`, `verbose`, Default: errors) |
0 commit comments