Changes in yml

Author: agarneha1331

browserstack.yml

@@ -5,20 +5,24 @@
 # BROWSERSTACK_ACCESS_KEY as env variables
 userName: YOUR_USERNAME
 accessKey: YOUR_ACCESS_KEY
+
 # ======================
-# Organizing your tests
+# BrowserStack Reporting
 # ======================
-# Use `projectName`, `buildName`, `name` capabilities to organise your tests
-# `name` is the name of your test sessions and is automatically picked from your
-# test name and doesn't need to be set manually when using BrowserStack SDK
-# `buildName` is used to name your CI/CD job or the execution of your test suite.
-# Ensure you add a dynamic identifier, like an incremental build number from your
-# CI/CD or timestamp at the end of every build; otherwise tests from different
-# executions will be grouped together on BrowserStack
-buildName: browserstack-build-1
-# Use `projectName` to set the name of your project. Example, Marketing Website
+# The following capabilities are used to set up reporting on BrowserStack:
+# Set 'projectName' to the name of your project. Example, Marketing Website
 projectName: BrowserStack Samples
+# Set `buildName` as the name of the job / testsuite being run
+buildName: browserstack build
+# `buildIdentifer` is a unique id to differentiate every execution that gets appended to
+# buildName. Choose your buildIdentifier format from the the available expressions:
+# ${BUILD_NUMBER} (Default): Generates an incremental counter with every execution
+# ${DATE_TIME}: Generates a Timestamp with every execution. Eg. 05-Nov-19:30
+# Read more about buildIdentifiers here -> https://www.browserstack.com/docs/automate/selenium/organize-tests
+buildIdentifier: '#${BUILD_NUMBER}' # Supports strings along with either/both ${expression}
+# Set `source` in the syntax `<fw-name>:sample-<branch-name>:<version-number>
 source: mocha:sample-master:v1.0
+
 # =======================================
 # Platforms (Browsers / Devices to test)
 # =======================================
@@ -27,18 +31,16 @@ source: mocha:sample-master:v1.0
 platforms:
   - os: OS X
     osVersion: Big Sur
-    browser: Chrome
+    browserName: Chrome
     browserVersion: latest
   - os: Windows
     osVersion: 10
-    browser: Edge
+    browserName: Edge
     browserVersion: latest
-  - device: iPhone 13
-    browserName: Safari
-    osVersion: 15
-  - device: Samsung Galaxy S22 Ultra
+  - deviceName: Samsung Galaxy S22 Ultra
     browserName: chrome # Try 'samsung' for Samsung browser
     osVersion: 12.0
+
 # =======================
 # Parallels per Platform
 # =======================
@@ -49,18 +51,21 @@ platforms:
 #
 # 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
 parallelsPerPlatform: 1
+
 # ==========================================
 # BrowserStack Local
 # (For localhost, staging/private websites)
 # ==========================================
 # Set browserStackLocal to true if your website under test is not accessible publicly over the internet
 # Learn more about how BrowserStack Local works here -> https://www.browserstack.com/docs/automate/selenium/local-testing-introduction
 browserstackLocal: true # <boolean> (Default false)
+
 # browserStackLocalOptions:
 # Options to be passed to BrowserStack local in-case of advanced configurations
   # localIdentifier: # <string> (Default: null) Needed if you need to run multiple instances of local.
   # forceLocal: true  # <boolean> (Default: false) Set to true if you need to resolve all your traffic via BrowserStack Local tunnel.
   # Entire list of arguments availabe here -> https://www.browserstack.com/docs/automate/selenium/manage-incoming-connections
+
 # ===================
 # Debugging features
 # ===================