Skip to main content

Test Observability on Playwright Node.js

Quick start guide to integrate BrowserStack Test Observability with Playwright Node.js

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 Playwright v1.31 or higher test suite, (it is okay even if you do not run your tests on BrowserStack infrastructure).
  • You use the Playwright test runner in your tests. The test variable used in writing the tests should be imported from @playwright/test.

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 Playwright.

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 Playwright project’s root directory and run the following commands to update or install the BrowserStack Node SDK and verify the installed version:

Terminal
npm i -D browserstack-node-sdk
npm list browserstack-node-sdk


Please ensure that you have at least browserstack-node-sdk v1.21.1 before proceeding.

Create the browserstack.yml file

Run the following command to create a browserstack.yml file:

Terminal
npx setup --username 'YOUR_USERNAME' --key 'YOUR_ACCESS_KEY'

Set up the browserstack.yml file

Update the following configurations in the browserstack.yml file:

browserstack.yml
userName: YOUR_USERNAME
accessKey: YOUR_ACCESS_KEY
buildName: "Your static build/job name goes here"
projectName: "Your static project name goes here"
CUSTOM_TAG_1: "You can set a custom Build Tag here"
# Use CUSTOM_TAG_<N> and set more build tags as you need.
testObservability: true
browserstackAutomation: false
...

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.

Please note that if you are running tests on BrowserStack Automate already, this SDK is only for Test Observability and will not override the capabilities you have configured in browserstack.config.js. This means if you want to have the same build & project names across Test Observability & BrowserStack Automate, you need to maintain the same values across both browserstack.config.js and browserstack.yml.

Run your test suite with Test Observability

Prepend browserstack-node-sdk to the existing command that you use to trigger a run as shown below and data will automatically start getting sent to BrowserStack Test Observability.

Terminal
npx browserstack-node-sdk <Your existing command for running your test suite>


For example, if you use the command npx playwright test sample --project=chromium to run your test suite, you need to replace it with npx browserstack-node-sdk playwright test sample --project=chromium.

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.


Visit Test Observability

Install or update to the latest version of BrowserStack Node SDK

Go to your Playwright 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:

Terminal
npm i -D browserstack-node-sdk
npm list browserstack-node-sdk


Please verify that you now have at least browserstack-node-sdk v1.21.1 before proceeding.

Set up the browserstack.yml file

Set up the browserstack.yml file as in the following code sample:

browserstack.yml
Copy icon Copy snippet

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 as shown below and data will automatically start getting sent to BrowserStack Test Observability.

Terminal
npx browserstack-node-sdk <Your existing command for running your test suite>


For example, if you use the command npx playwright test sample --project=chromium to run your test suite, you need to replace it with npx browserstack-node-sdk playwright test sample --project=chromium.

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.


Visit Test Observability

Install or update to the latest version of BrowserStack Node SDK

Go to your Playwright project’s root directory and run the following commands to update or install the BrowserStack Node SDK and verify the installed version:

Terminal
npm i -D browserstack-node-sdk
npm list browserstack-node-sdk


Please ensure that you now have at least browserstack-node-sdk v1.21.1 before proceeding.

Create the browserstack.yml file

If you don’t already have a browserstack.yml file, run the following command to create one:

Terminal
npx setup --username 'YOUR_USERNAME' --key 'YOUR_ACCESS_KEY'

Set up the browserstack.yml file

Set up the browserstack.yml file as follows:

browserstack.yml
userName: YOUR_USERNAME
accessKey: YOUR_ACCESS_KEY
buildName: "Your static build/job name goes here"
projectName: "Your static project name goes here"
CUSTOM_TAG_1: "You can set a custom Build Tag here"
# Use CUSTOM_TAG_<N> and set more build tags as you need.
testObservability: true
browserstackAutomation: false
...

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 as shown below and data will automatically start getting sent to BrowserStack Test Observability.

Terminal
npx browserstack-node-sdk <Your existing command for running your test suite>


For example, if you use the command npx playwright test sample --project=chromium to run your test suite, you need to replace it with npx browserstack-node-sdk playwright test sample --project=chromium.

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.


Visit Test Observability

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

Is this page helping you?

Yes
No

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!

Talk to an Expert
Download Copy