cross-browser-testing
Installation
SKILL.md
Before starting: Check for .agents/qa-project-context.md in the project root. It contains target browsers, analytics data, and platform priorities that drive matrix design.
Discovery Questions
- Target browsers from analytics: What do actual users use? Pull browser/OS data from your analytics tool. Testing browsers nobody uses is waste; missing a browser 15% of users rely on is a bug.
- Desktop and mobile? Mobile Safari on iOS and Chrome on Android have different rendering behaviors than their desktop counterparts. Treat them as separate matrix entries.
- Cloud platform: BrowserStack, Sauce Labs, LambdaTest, or local browsers only? Cloud platforms provide real browser instances; Playwright's built-in browsers cover Chromium, Firefox, and WebKit.
- Progressive enhancement or pixel-perfect? Progressive enhancement accepts graceful degradation. Pixel-perfect demands identical rendering. The answer determines pass/fail criteria.
- Existing Playwright config? If the project already uses Playwright, cross-browser testing is a configuration change, not a new tool.
Core Principles
Related skills