Test Observability on CodeceptJS
Quick start guide to integrate BrowserStack Test Observability with CodeceptJS
Prerequisites
- You have an account with BrowserStack (even a free trial works) and can get your Username and Access Key from Settings.
- You have a CodeceptJS test suite, (it is okay even if you do not run your tests on BrowserStack infrastructure).
- You use Node version 14 or higher.
Integrate with Test Observability
BrowserStack Test Observability can be used regardless of where your tests run - whether on BrowserStack’s devices and browsers, locally on your laptop, CI machines, or using another cloud provider.
Not only that, Test Observability is agnostic to the type of testing and hence you could also integrate it with your unit or integration test suite written using CodeceptJS.
Test Observability supports WebDriverIO, Playwright, and other runners with CodeceptJS.
Please select your setup below to get started with an awesome debugging experience with Test Observability:
Install or update to the latest version of BrowserStack Node SDK
Go to your CodeceptJS project’s root directory and run the following commands to update or install the BrowserStack Node SDK and verify the installed version:
Please ensure that you have at least browserstack-node-sdk v1.32.6 before proceeding.
Modify the browserstack.yml file
Update the following configurations in the browserstack.yml file:
The projectName and buildName config must be static and not change across different runs of the same build. Restrict the characters in your projectName and buildName to alphanumeric characters (A-Z, a-z, 0-9), underscores (_), colons (:), and hyphens (-). Any other character will be replaced with a space.
Run your test suite with Test Observability
Prepend browserstack-node-sdk to the existing command that you use to trigger a run and data will automatically start getting sent to BrowserStack Test Observability.
Post build run completion, you will see the build URL of Test Observability. Alternatively, you can also navigate to your build run using Build Runs.
Install or update to the latest version of BrowserStack Node SDK
Go to your CodeceptJS project’s root directory and run the following commands to update or install the BrowserStack Node SDK and ensure that you have the latest version:
Ensure that you now have at least browserstack-node-sdk v1.32.6 before proceeding.
Set up the browserstack.yml file
Set up the browserstack.yml file as in the following code sample:
The projectName and buildName config must be static and not change across different runs of the same build. Restrict the characters in your projectName and buildName to alphanumeric characters (A-Z, a-z, 0-9), underscores (_), colons (:), and hyphens (-). Any other character will be replaced with a space.
Run your test suite with Test Observability
Prepend browserstack-node-sdk to the existing command that you use to trigger a run and data will automatically start getting sent to BrowserStack Test Observability.
Post build run completion, you will see the build URL of Test Observability. Alternatively, you can also navigate to your build run using Build Runs.
Install or update to the latest version of BrowserStack Node SDK
Go to your CodeceptJS project’s root directory and run the following commands to update or install the BrowserStack Node SDK and verify the installed version:
Please ensure that you now have at least browserstack-node-sdk v1.32.6 before proceeding.
Create the browserstack.yml file
Run the following command to set your username and accesskey as environment variables:
Modify the browserstack.yml file
Set up the browserstack.yml file as follows:
The projectName and buildName config must be static and not change across different runs of the same build. Restrict the characters in your projectName and buildName to alphanumeric characters (A-Z, a-z, 0-9), underscores (_), colons (:), and hyphens (-). Any other character will be replaced with a space.
Run your test suite with Test Observability
Prepend browserstack-node-sdk to the existing command that you use to trigger a run and data will automatically start getting sent to BrowserStack Test Observability.
Post build run completion, you will see the build URL of Test Observability. Alternatively, you can also navigate to your build run using Build Runs.
Using CodeceptJS with different runners
CodeceptJS with Playwright
To use CodeceptJS with Playwright or WebdriverIO, add the correct helper to the codecept.conf.js file.
The browserstack-node-sdk can be used with both the helpers to run tests on the BrowserStack infrastructure, or to run tests locally. You can set browserstackAutomation to true or false in the browserstack.yml file depending on where you want to execute your tests.
CodeceptJS with BDD
Test Observability supports BDD configuration in CodeceptJS. For this, ensure that your codecept.conf.js file is set up as described in the Codecept documentation.
CodeceptJS without Playwright or WebdriverIO
To use CodeceptJS with runners other than Playwright or WebdriverIO, add the correct helper to the codecept.conf.js file.
However, please ensure that browserstackAutomation is set to false in the browserstack.yml file. This is because BrowserStack Automate supports the direct execution of only Playwright and WebdriverIO test runners.
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!