TE

testing-browser-compatibility

Tests web applications across different browsers and real devices using Playwright or cloud providers like BrowserStack.

Install

mkdir -p .claude/skills/testing-browser-compatibility && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9440" && unzip -o skill.zip -d .claude/skills/testing-browser-compatibility && rm skill.zip

Installs to .claude/skills/testing-browser-compatibility

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Test across multiple browsers and devices for cross-browser compatibility.
74 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Test web applications across multiple browsers and rendering engines
  • Validate CSS rendering and layout consistency across viewports
  • Verify JavaScript API support and polyfill requirements
  • Execute automated tests on real physical devices via cloud providers
  • Capture visual diffs and video traces for failing tests

How it works

It uses Playwright for local multi-browser emulation and integrates with cloud providers like BrowserStack or Kobiton for real-device testing.

Inputs & outputs

You give it
Test URL and browser configuration matrix
You get back
Compatibility report with screenshots and failure logs

When to use testing-browser-compatibility

  • Testing UI consistency across Chrome, Firefox, and Safari
  • Running automated tests on real mobile devices
  • Validating CSS layout across different screen sizes
  • Verifying cross-browser JavaScript functionality

About this skill

Browser Compatibility Tester

Table of Contents

Overview | Instructions (Local / Cloud) | Examples | Error Handling | Output | Resources

Overview

Test web applications across multiple browsers, rendering engines, and real devices. Validates CSS rendering, JavaScript API support, layout consistency, and interactive behavior across Chromium (Chrome, Edge), Gecko (Firefox), and WebKit (Safari) -- locally with Playwright or on real devices via BrowserStack, Sauce Labs, LambdaTest, or Kobiton.

Prerequisites

  • Playwright installed (npx playwright install --with-deps) and application running at a test URL
  • For cloud testing: provider credentials in environment variables (see ${CLAUDE_SKILL_DIR}/references/cloud-providers.md)

Instructions

Mode 1: Local Testing (Playwright)

Default mode. Zero cloud accounts needed.

  1. Define the browser matrix from project browserslist config or use defaults:

    • Desktop: Chrome (latest), Firefox (latest), Safari (latest), Edge (latest)
    • Mobile: iPhone 14 (WebKit), Pixel 7 (Chromium)
    • Viewports: 375px, 768px, 1280px, 1920px
  2. Scan the codebase for compatibility risks:

    • Grep for modern JS APIs (IntersectionObserver, structuredClone, Array.at(), Promise.withResolvers())
    • Grep for modern CSS (container queries, has(), @layer, subgrid, color-mix())
    • Cross-reference against caniuse data; flag usage without polyfills or @supports
  3. Write compatibility-focused tests:

    • Layout: key elements render at expected positions/sizes per viewport
    • CSS features: modern features degrade gracefully behind @supports
    • JS APIs: polyfills load in older browsers; form inputs (date, color, range) across engines
    • Accessibility: run axe-core per browser (@axe-core/playwright)
  4. Execute and capture results:

    • npx playwright test --project=chromium --project=firefox --project=webkit
    • Screenshots per browser for visual comparison
    • Video traces for failing tests

Mode 2: Cloud Real-Device Testing

Applies when real physical devices, broader OS coverage, or carrier network conditions are required beyond what Playwright emulation can replicate. Read ${CLAUDE_SKILL_DIR}/references/cloud-providers.md for full auth, API, and capabilities details.

Provider selection:

NeedProvider
Broadest browser/OS matrix (3,000+ combos)BrowserStack
Enterprise CI/CD, Sauce Connect tunnelSauce Labs
Auto-healing selectors, smart testingLambdaTest
Real physical devices, scriptless automationKobiton

Never hardcode credentials. Set provider env vars (BROWSERSTACK_USERNAME/ACCESS_KEY, SAUCE_USERNAME/ACCESS_KEY, LT_USERNAME/ACCESS_KEY, KOBITON_USERNAME/API_KEY).

  1. Verify credentials are set for the chosen provider
  2. Query available devices/browsers via provider API
  3. Configure WebDriver or Appium capabilities (see ${CLAUDE_SKILL_DIR}/references/cloud-providers.md)
  4. Execute tests against cloud grid
  5. Retrieve session artifacts (screenshots, video, logs, network HAR)
  6. Aggregate results into compatibility report (CI/CD patterns: ${CLAUDE_SKILL_DIR}/references/ci-cd-integration.md)

Browser-Specific Checks

  • Safari: date input formatting, scroll behavior, backdrop-filter, PWA manifest, position: sticky in overflow
  • Firefox: scrollbar styling, gap in flexbox, subpixel rendering, print stylesheets
  • Mobile: touch events, viewport meta, safe area insets, virtual keyboard resize

Pre-built device matrices: ${CLAUDE_SKILL_DIR}/references/device-matrix.md (top 10, mobile-first, enterprise, Kobiton real-device).

Examples

Playwright multi-browser config:

import { defineConfig, devices } from '@playwright/test';
export default defineConfig({
  projects: [
    { name: 'chromium', use: { ...devices['Desktop Chrome'] } },
    { name: 'firefox', use: { ...devices['Desktop Firefox'] } },
    { name: 'webkit', use: { ...devices['Desktop Safari'] } },
    { name: 'mobile-chrome', use: { ...devices['Pixel 7'] } },
    { name: 'mobile-safari', use: { ...devices['iPhone 14'] } },
  ],
});

Cross-browser layout test:

test('nav renders correctly across browsers', async ({ page }) => {
  await page.goto('/');
  const nav = page.locator('nav');
  await expect(nav).toBeVisible();
  const box = await nav.boundingBox();
  expect(box.width).toBeGreaterThan(300);
});

Kobiton real-device capabilities:

{
  "platformName": "iOS",
  "appium:deviceName": "iPhone 15 Pro",
  "appium:platformVersion": "17",
  "browserName": "Safari",
  "kobiton:options": {
    "sessionName": "Safari Compat Test",
    "deviceGroup": "KOBITON",
    "captureScreenshots": true
  }
}

Error Handling

ErrorCauseSolution
WebKit fails, Chromium passesCSS property unsupported in SafariAdd -webkit- prefix or @supports fallback
Date input renders differentlyBrowsers implement <input type="date"> differentlyUse custom date picker component
Test passes locally, fails on cloudReal device rendering differs from emulationRun critical paths on real devices for final validation
Kobiton device unavailableDevice in use or offlineQuery GET /v1/devices for online devices; use deviceGroup for flexible matching
Cloud session timeoutLong test on slow deviceIncrease sessionTimeout; split into smaller test files

Output

  • Playwright config with multi-browser projects and test files in tests/compatibility/
  • Compatibility matrix report (pass/fail per browser, viewport, device)
  • Screenshots per browser for visual diff; unsupported API list with polyfill recommendations
  • Cloud session URLs with video replay links (when using cloud providers)

Resources

When not to use it

  • When testing non-web applications

Prerequisites

Playwright installedApplication running at a test URL

Limitations

  • Real device rendering may differ from emulation
  • Cloud session timeouts occur on slow devices

How it compares

It automates cross-platform verification instead of relying on manual browser-by-browser testing.

Compared to similar skills

testing-browser-compatibility side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
testing-browser-compatibility (this skill)027dReviewIntermediate
chrome-devtools417moReviewIntermediate
code-coverage-with-gcov154moReviewIntermediate
angular-best-practices213moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

Search skills

Search the agent skills registry