|
| 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: BROWSERSTACK_USERNAME |
| 7 | +accessKey: BROWSERSTACK_ACCESS_KEY |
| 8 | + |
| 9 | +# ====================== |
| 10 | +# BrowserStack Reporting |
| 11 | +# ====================== |
| 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 | + |
| 24 | +source: jest-js:appium-sample-main:v1.0 |
| 25 | + |
| 26 | +# Set `app` to define the app that is to be used for testing. |
| 27 | +# It can either take the id of any uploaded app or the path of the app directly. |
| 28 | +app: ./WikipediaSample.apk |
| 29 | +# app: ./LocalSample.apk #For running local tests |
| 30 | + |
| 31 | +# ======================================= |
| 32 | +# Platforms (Browsers / Devices to test) |
| 33 | +# ======================================= |
| 34 | +# Platforms object contains all the browser / device combinations you want to test on. |
| 35 | +# Entire list available here -> (https://www.browserstack.com/list-of-browsers-and-platforms/automate) |
| 36 | + |
| 37 | +platforms: |
| 38 | + - deviceName: Samsung Galaxy S22 Ultra |
| 39 | + osVersion: 12.0 |
| 40 | + platformName: android |
| 41 | + - deviceName: OnePlus 11R |
| 42 | + osVersion: 13.0 |
| 43 | + platformName: android |
| 44 | + - deviceName: Google Pixel 6 Pro |
| 45 | + osVersion: 12.0 |
| 46 | + platformName: android |
| 47 | + |
| 48 | +# ========================================== |
| 49 | +# BrowserStack Local |
| 50 | +# (For localhost, staging/private websites) |
| 51 | +# ========================================== |
| 52 | +# Set browserStackLocal to true if your website under test is not accessible publicly over the internet |
| 53 | +# Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction |
| 54 | +browserstackLocal: true # <boolean> (Default false) |
| 55 | +#browserStackLocalOptions: |
| 56 | +#Options to be passed to BrowserStack local in-case of advanced configurations |
| 57 | +# localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local. |
| 58 | +# forceLocal: true # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel. |
| 59 | +# Entire list of arguments available here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections |
| 60 | + |
| 61 | +# =================== |
| 62 | +# Debugging features |
| 63 | +# =================== |
| 64 | +debug: false # <boolean> # Set to true if you need screenshots for every selenium command ran |
| 65 | +networkLogs: false # <boolean> Set to true to enable HAR logs capturing |
| 66 | +consoleLogs: errors # <string> Remote browser's console debug levels to be printed (Default: errors) |
| 67 | +# Available options are `disable`, `errors`, `warnings`, `info`, `verbose` (Default: errors) |
0 commit comments