BrowserStack Integration — Development

Q: What environment variables are required?

You need `BROWSERSTACK_USERNAME` and `BROWSERSTACK_ACCESS_KEY` set. If not set, the skill will inform you how to get them from browserstack.com/accounts/settings and stop.

This skill integrates Playwright tests with BrowserStack's cloud grid for cross-browser and cross-device testing. It configures the Playwright config for BrowserStack, runs tests on cloud browsers, retrieves build results, lists available browsers, and supports local testing via tunnels.

engineering claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Configures playwright.config.ts with BrowserStack connect options for Chrome, Firefox, and WebKit on specific OS version
Adds an npm script for running cloud tests.
Runs Playwright tests on BrowserStack with specified projects.
Retrieves build results and formats them into a summary table with status, browser, OS, duration, video, and log URLs.
Lists available Playwright-compatible browsers from BrowserStack.
Provides instructions for setting up BrowserStack Local for testing localhost.

🎯 When to use it

When the user mentions 'browserstack', cross-browser, 'cloud testing', 'browser matrix', 'test on safari', 'test on firefox', or 'browser
When you need to run Playwright tests on a variety of browser/OS combinations without local emulators.
When you want to check results of BrowserStack test runs, including videos and logs.
When you need to set up local testing for localhost or staging behind a firewall.

🚀 How to use

Trigger: /pw:browserstack

Trigger by using slash commands like /pw:browserstack setup, /pw:browserstack run, /pw:browserstack results, /pw:browserstack browsers, or /pw:browserstack local. Ensure the environment variables BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY are set. The skill will guide you through configuration and execution. Example prompts:

/pw:browserstack setup
/pw:browserstack run

📄 Output: Cross-browser test results table with per-browser pass/fail status and links to BrowserStack dashboard.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering-team/playwright-pro/skills/browserstack .claude/skills/browserstack

Skill source: engineering-team/playwright-pro/skills/browserstack/SKILL.md

⚠️ Good to know

Requires BrowserStack credentials and manual registration of the BrowserStack MCP server; the MCP tools and the /pw:browserstack command will fail with 'tool not found' until the server is enabled manually.

❓ FAQ

What environment variables are required?

You need BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY set. If not set, the skill will inform you how to get them from browserstack.com/accounts/settings and stop.

Why do I get 'tool not found' when using the skill?

The BrowserStack MCP server is not auto-registered due to issue #978. You must manually enable it by following the Integrations section in the plugin's CLAUDE.md, which involves installing dependencies and registering the server in your MCP config.

What does the 'local' command do?

It helps set up BrowserStack Local for testing localhost or staging behind a firewall by installing browserstack-local and providing setup instructions.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.