borghei/Claude-Skills / engineering/playwright-pro
playwright-pro
VerifiedEnd-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.6 KB |
| assets/flawed_tests/profile.spec.ts | script | 468 B |
| assets/reports/run1.json | config | 1.2 KB |
| assets/reports/run2.json | config | 1.3 KB |
| assets/reports/run3.json | config | 1.4 KB |
| assets/sample_flows.json | config | 800 B |
| assets/sample_login.html | other | 489 B |
| assets/tests/login.spec.ts | script | 906 B |
| references/core-rules-and-patterns.md | markdown | 7.2 KB |
| references/diagnosis-migration-and-ci.md | markdown | 8.7 KB |
| references/playwright-patterns.md | markdown | 4.5 KB |
| scripts/coverage_mapper.py | script | 11.0 KB |
| scripts/flaky_detector.py | script | 10.6 KB |
| scripts/page_object_generator.pyexecutable | script | 14.8 KB |
| scripts/test_analyzer.pyexecutable | script | 12.3 KB |
| scripts/test_generator.py | script | 11.1 KB |
| scripts/test_report_parser.pyexecutable | script | 14.8 KB |
| skills/browserstack.md | markdown | 2.4 KB |
| skills/coverage.md | markdown | 1.9 KB |
| skills/fix.md | markdown | 2.6 KB |
| skills/generate.md | markdown | 2.4 KB |
| skills/init.md | markdown | 2.1 KB |
| skills/migrate.md | markdown | 2.5 KB |
| skills/report.md | markdown | 2.0 KB |
| skills/review.md | markdown | 2.2 KB |
| skills/testrail.md | markdown | 2.5 KB |
skills/browserstack.md
View on GitHub# Sub-Skill: BrowserStack Integration
**Parent:** playwright-pro
**Trigger:** "BrowserStack", "cloud testing", "cross-browser cloud"
## Purpose
Configure Playwright to run tests on BrowserStack's cloud infrastructure for cross-browser and cross-device testing at scale.
## Workflow
### Step 1: Install BrowserStack SDK
```bash
pnpm add -D browserstack-node-sdk
```
### Step 2: Configure BrowserStack
Create `browserstack.yml` in project root:
```yaml
userName: ${BROWSERSTACK_USERNAME}
accessKey: ${BROWSERSTACK_ACCESS_KEY}
platforms:
- os: Windows
osVersion: 11
browserName: Chrome
browserVersion: latest
- os: OS X
osVersion: Sonoma
browserName: Safari
browserVersion: latest
- deviceName: iPhone 15
osVersion: 17
browserName: Safari
- deviceName: Samsung Galaxy S24
osVersion: 14.0
browserName: Chrome
parallelsPerPlatform: 2
projectName: "My Project E2E"
buildName: "Build ${BUILD_NUMBER}"
debug: true
networkLogs: true
```
### Step 3: Update Playwright Config
Add BrowserStack-specific project entries or use the SDK's automatic browser provisioning. The SDK wraps `playwright test` and routes browser connections through BrowserStack.
### Step 4: Run on BrowserStack
```bash
npx browserstack-node-sdk playwright test
```
### Step 5: CI Integration
Add BrowserStack credentials as CI secrets and run the cloud suite on a schedule or for release candidates (not every PR -- too slow and expensive).
```yaml
# GitHub Actions
- run: npx browserstack-node-sdk playwright test
env:
BROWSERSTACK_USERNAME: ${{ secrets.BROWSERSTACK_USERNAME }}
BROWSERSTACK_ACCESS_KEY: ${{ secrets.BROWSERSTACK_ACCESS_KEY }}
```
## Best Practices
1. Run cloud tests on a schedule (nightly) or for release candidates, not every commit
2. Keep a fast local suite (Chromium only) for PR feedback loops
3. Use BrowserStack for Safari/IE/mobile-specific validation
4. Set `debug: true` and `networkLogs: true` for failure investigation
5. Tag builds with commit SHA for traceability
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| BrowserStack credentials | Yes | Username and access key |
| Target platforms | No | Defaults to Chrome + Safari + mobile |
| Parallel count | No | Defaults to 2 per platform |
## Outputs
- `browserstack.yml` configuration
- Updated CI workflow with cloud testing step
- Test results on BrowserStack dashboard
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |