browserstack

Topics in the source

• BrowserStack Integration
• Prerequisites
• Capabilities
• 1. Configure for BrowserStack
• 2. Run Tests on BrowserStack
• 3. Get Build Results
• 4. Check Available Browsers
• 5. Local Testing

Run Playwright tests on BrowserStack's cloud grid for cross-browser and cross-device testing. Environment variables must be set: BROWSERSTACKUSERNAME — your BrowserStack username BROWSERSTACKACCESSKEY — your access key If not set, inform the user how to get them from browserstack.com/accounts/settings and stop. The BrowserStack MCP server is not auto-registered (issue #978). pw-browserstack was removed from the plugin's .mcp.json because it failed to connect for every user (the plugin ships no nodemodules). The browserstack MCP tools used below, and the /pw:browserstack command, will fail with "tool not found" until it is enabled manually — see the Integrations section of the plugin's CLAUDE.md (cd integrations/browserstack-mcp && npm install, then register the server in your own user/project MCP config). Setting the env vars alone is not sufficient. Steps: 1. Check current playwright.config.ts 2. Add BrowserStack connect options: 3. Add npm script: "test:e2e:cloud": "npx playwright test --project='chrome@' --project='firefox@' --project='webkit@'" Steps: 1. Verify credentials are set 2. Run tests with BrowserStack projects: 3. Monitor execution 4. Report results per browser Steps:

This is an excerpt. Refer to the complete source and its current requirements.