Join our Discord
Automated tests on Behave
Quick start guide to integrate Automated tests on BrowserStack Accessibility Testing with Behave.
Prerequisites
- You have Behave v1.2.6 or later, Python3, and Pip3 installed on your machine.
- You have a pre-existing Behave test suite.
Integrate with Automated tests
Follow these steps to get started with adding Automated tests to your test suite:
The minimum version of BrowserStack SDK that supports Automated tests is v1.21.0.
To get the instructions to integrate Automated tests in your test suites, select one of the following tabs depending on where your test suites run:
Install BrowserStack Python-Behave SDK
Execute the following commands to install the BrowserStack Behave SDK.
Create the browserstack.yml file
You’ll have to create the browserstack.yml file as in the following sample. Else, verify that your config file has all the required key-value pairs.
Especially, ensure to add the accessibility flag at the end of the browserstack.yml file.
Create the browserstack.yml file in the root folder of your test suite if it doesn’t exist.
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.
-
Accessibility testing runs on Desktops (Mac & Windows) with Chrome 100 & later on Automate.
-
Window handle commands might cause instability to Automated tests. If you face issues, consider removing window handle commands or contact support.
Run your suite with Automated tests
Add browserstack-sdk before your existing run commands to execute your tests on BrowserStack using the Behave SDK.
You can check the Accessibility report for your build through the Automated tests page.
Install BrowserStack Python-Behave SDK
Execute the following commands to install the BrowserStack Behave SDK.
Create the browserstack.yml file
You’ll have to create the browserstack.yml file as in the following sample. Else, verify that your config file has all the required key-value pairs.
Especially, ensure you add the accessibility flag at the end of the browserstack.yml file.
Create the browserstack.yml file in the root folder of your test suite if it doesn’t exist.
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.
-
Accessibility testing runs on Desktops (Mac & Windows) with Chrome 100 & later on Automate.
-
Window handle commands might cause instability to Automated tests. If you face issues, consider removing window handle commands or contact support.
Run your suite with Automated tests
Add browserstack-sdk before your existing run commands to execute your tests on BrowserStack using the Behave SDK.
You can check the Accessibility report for your build through the Automated tests page.
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!