Automated tests mandatorily need the following configurations in the browserstack.yml file. In particular, set the accessibility flag as true at the end of the browserstack.yml file.
The projectName and buildName config must be static and not change across different runs of the same build. This deviates from the standard BrowserStack Automate approach, because Automated tests automatically identify different build runs.
```yml
userName: YOUR_USERNAME
accessKey: YOUR_ACCESS_KEY
buildName: "Your static build/job name of CI goes here"
projectName: "Your static project name goes here"
framework: junit4
...
accessibility: true
platforms:
- os: Windows
osVersion: 10
browserName: Chrome
browserVersion: latest
```
Automated tests support the following browsers and operating systems:
Operating system
Chrome
Safari
Edge
Windows
Versions 100 and above
N/A
Not supported
macOS
Versions 100 and above
Not supported
Not supported
Android
Android 15 and 16
N/A
Not supported
iOS
Not supported
Not supported
Not supported
Use the exact configurations provided in the example for mobile browser testing. Using different combinations of configurations may cause testing errors.
Window handle commands might cause instability to Automated tests. If you face issues, consider removing window handle commands or contact support.
Run your test suite with Automated tests
Continue running your tests as you have been running previously. The command to run your tests using the BrowserStack SDK remains unchanged. For your reference, here’s a sample command:
Automated tests mandatorily need the following configurations in the browserstack.yml file. In particular, set the accessibility flag as true at the end of the browserstack.yml file.
The projectName and buildName config must be static and not change across different runs of the same build. This deviates from the standard BrowserStack Automate approach, because Automated tests automatically identify different build runs.
```yml
userName: YOUR_USERNAME
accessKey: YOUR_ACCESS_KEY
buildName: "Your static build/job name of CI goes here"
projectName: "Your static project name goes here"
framework: junit4
...
turboscale: true
accessibility: true
platforms:
- os: Windows
osVersion: 10
browserName: Chrome
browserVersion: latest
```
Automated tests support the following browsers and operating systems:
Operating system
Chrome
Safari
Edge
Windows
Versions 100 and above
N/A
Not supported
macOS
Versions 100 and above
Not supported
Not supported
Android
Android 15 and 16
N/A
Not supported
iOS
Not supported
Not supported
Not supported
Use the exact configurations provided in the example for mobile browser testing. Using different combinations of configurations may cause testing errors.
Window handle commands might cause instability to Automated tests. If you face issues, consider removing window handle commands or contact support.
Run your test suite with Automated tests
Continue running your tests as you have been running previously. The command to run your tests using the BrowserStack SDK remains unchanged. For your reference, here’s a sample command:
Automated tests mandatorily need the following configurations in the browserstack.yml file. In particular, set the accessibility flag as true at the end of the browserstack.yml file.
The projectName and buildName config must be static and not change across different runs of the same build. This deviates from the standard BrowserStack Automate approach, because Automated tests automatically identify different build runs.
Google Chrome policy changes in v142 and later prevent accessibility automation from functioning for customers using non-BrowserStack infrastructure.
To continue performing accessibility automation, you must either:
Automated tests support the following browsers and operating systems:
Operating system
Chrome
Safari
Edge
Windows
Versions 100 and above
N/A
Not supported
macOS
Versions 100 and above
Not supported
Not supported
Android
Android 15 and 16
N/A
Not supported
iOS
Not supported
Not supported
Not supported
Use the exact configurations provided in the example for mobile browser testing. Using different combinations of configurations may cause testing errors.
Window handle commands might cause instability to Automated tests. If you face issues, consider removing window handle commands or contact support.
Run your test suite with Automated tests
Continue running your tests as you have been running previously. The command to run your tests using the BrowserStack SDK remains unchanged. For your reference, here’s a sample command:
Join our Discord