Automated tests on Codecept
Quick start guide to integrate Automated tests on BrowserStack Accessibility Testing with Codecept.
Prerequisites
- You have an account with BrowserStack (even a free trial works) and can get the username and access key from Account & Profile.
- You have a pre-existing Codecept test suite integrated with BrowserStack Automate.
Integrate with Automated tests
Follow these steps to get started with adding Automated tests to your test suite:
The minimum version of browserstack-node-sdk that supports Automated tests is 1.31.22.
Install the latest version of the BrowserStack SDK
Install (or update) the browserstack-node-sdk npm package using the following command.
BrowserStack SDK is a very powerful tool which you can use to set the different browser/device combinations and parallelization. For more details, check out the Automate Integration guide.
Make changes to the SDK config file
If you’ve installed the browserstack-node-sdk for the first time, you’ll have to create the following browserstack.yml file. 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 is a deviation in approach as specified by BrowserStack Automate since Automated tests will automatically identify different build runs.
-
Accessibility testing runs only on Desktops (Mac & Windows) with Chrome 100 & above 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
Continue running your tests as you have been running previously. The command to run your tests using the BrowserStack SDK remains unchanged. You can check the Accessibility report for your build through the Automated tests page.
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!