Join our Discord
Troubleshoot errors in Automated tests
Solve common errors that you might face while using Automated tests.
Automated tests is an automated solution to add accessibility testing to your pre-existing test suite. You can find solutions to common problems in the following section.
Common errors and solutions
You can contact support if your issue is not listed in the following table:
| Problem | Solution |
|---|---|
Automated tests on Playwright failing with the following error:Error: Playwright Version Not Supported
|
Update Playwright version using the following command:npm install @playwright/test@latest
|
| Accessibility tests not running due to an unsupported version of BrowserStack SDK. | Review the framework documentation for information on supported SDK versions or instructions for updating to the latest BrowserStack SDK version. |
| Running Automated tests without BrowserStack SDK. | Install the latest version of BrowserStack SDK by following the instructions for your framework. |
| User not on the right plan. | Upgrade to a plan that suits your needs. |
Incorrect accessibilityOptions
|
Refer to the available accessibilityOptions and fix any errors. |
| Invalid browser or browser versions | Automated tests work only on Chrome version 100 and later. |
| Using Chrome browser in legacy headless mode | Use headed mode or the new headless mode introduced with Chrome 112. |
| Using Chrome browser in incognito mode | Automated tests currently does not support incognito mode. |
As per the includeTagsInTestingScope and excludeTagsInTestingScope, there are no applicable test cases for accessibility testing. |
Refer to the configuration options and fix the tags specified in includeTagsInTestingScope and excludeTagsInTestingScope to ensure there are test cases assigned for accessibility testing. |
Extension installation failure if the user passes chromeOptions that do not allow extensions - with excludeSwitches set to load-extension or flags such as disable-extensions or disable-extensions-except. |
Fix the chromeOptions and reinstall the BrowserStack Accessibility Toolkit
|
| Additional tips | Do not quit the driver inside the test case itself. Also, do not invoke driver.close method as it is not patched. Similarly, do not initialize the driver inside the test case. Instead, do it in a before method. |
Supported framework-browser combinations
Automated tests throw an error if run on unsupported framework-browser combinations. The following table lists the framework-browser combinations that support Automated tests:
| Framework | Supported Browser(s) |
|---|---|
| Selenium + TestNG (Java) | Chrome, Safari |
| Java Cucumber + TestNG | Chrome, Safari |
| Selenium + Mocha (JS) | Chrome, Safari |
| Cypress | Chrome |
| Playwright | Chrome |
| WebdriverIO | Chrome |
| Nightwatch.js | Chrome |
| Jest | Chrome |
| NUnit | Chrome |
| xUnit | Chrome |
| SpecFlow | Chrome |
Allow extensions
Accessibility tests fail if your browser blocks extensions. Remove any extension blockers for smooth execution of accessibility tests.
In Chrome browser, the extension might fail if the user passes chromeOptions that do not allow extensions, with excludeSwitches set to load-extension or flags such as disable-extensions or disable-extensions-except. In this case, fix the chromeOptions and reinstall the BrowserStack Accessibility Toolkit.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!