Automated tests on Cucumber-JUnit5
Quick start guide to integrate Automated tests in BrowserStack Accessibility Testing with Cucumber-JUnit5.
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 Cucumber-JUnit5 test suite integrated with BrowserStack Automate.
-
Maven is installed on your machine, its environment variables are set, and its bin is added to the system path,
$PATH
. - Cucumber-Java v5+, Java v8+, Selenium v2.5+ (JSON Wire / W3C).
Integrate with Automated tests
Follow these steps to get started with adding Automated tests to your test suite:
The minimum version of browserstack-java-sdk
that supports Automated tests with Cucumber-JUnit5 is 1.19.0
.
Modify your browserStack.yml config file
Automated tests mandatorily need the following configurations in the browserstack.yml
file. Especially, ensure to 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 is a deviation in approach as specified by BrowserStack Automate since Automated tests will automatically identify different build runs.
Accessibility testing will only run on Desktops (Mac & Windows) with Chrome 98 & above on Automate.
Run your test suite with Automated tests
You can continue running your tests as you have been 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.
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!