compatibility-testing
compatibility-testing helps you systematically verify that web applications perform consistently across different browsers and device configurations. Run comprehensive validation checks to catch rendering issues and functional gaps before they reach users, ensuring a reliable experience for everyone.
compatibility-testing enables you to systematically verify that web applications perform consistently across different browsers and device configurations. By running comprehensive validation checks before release, you catch rendering issues and functional gaps that might otherwise reach users, ensuring a reliable experience for everyone regardless of which browser or device they use.
AI-generated summary based on this skill's SKILL.md
Install
proffesor-for-testing/agentic-qe/compatibility-testing · repository language: TypeScript
git clone https://github.com/proffesor-for-testing/agentic-qe
cp -r agentic-qe/.claude/skills/compatibility-testing ~/.claude/skills/compatibility-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does compatibility-testing help ensure consistent experience across all browsers?
compatibility-testing enables you to systematically verify that web applications perform consistently across different browsers and device configurations. By running comprehensive validation checks before release, you catch rendering issues and functional gaps that might otherwise reach users, ensuring a reliable experience for everyone regardless of which browser or device they use.
What is the best way to test a website on different browsers and devices?
compatibility-testing supports multiple approaches: you can set up automated cross-browser testing using Playwright or cloud services like BrowserStack to run tests across Safari, Firefox, Chrome, and Edge simultaneously. The skill enables you to test responsive design at specific breakpoints (mobile, tablet, desktop) and run parallel compatibility tests across browser and device combinations to reduce testing time while maintaining comprehensive coverage.
Can compatibility-testing automate cross-device testing across cloud services?
Yes, compatibility-testing facilitates automated cross-browser testing setup using cloud services like BrowserStack integrated with Playwright. This approach allows you to run parallel compatibility tests across multiple browser and device combinations without maintaining your own device lab, significantly reducing testing time while validating your application across the full matrix of target platforms.
How can I test responsive design at specific breakpoints like 320px, 768px, and 1920px?
compatibility-testing enables you to test responsive design at specific breakpoints across mobile, tablet, and desktop viewports. The skill supports viewport emulation testing and visual regression testing across multiple browsers, allowing you to capture and compare visual differences at critical breakpoints to identify and document any rendering inconsistencies before release.
What does compatibility-testing do to identify visual inconsistencies across platforms?
compatibility-testing helps you identify and document visual inconsistencies and rendering issues across platforms through visual regression testing capabilities. By running tests across different browser and device combinations, you can capture visual differences, compare outputs, and create a comprehensive record of any platform-specific issues that need resolution before your application reaches users.
How can I validate browser support before releasing my web application?
compatibility-testing validates that a web application renders and functions consistently across multiple browsers and devices before release. Set up automated validation checks using Playwright or BrowserStack to test across your target browser matrix, run parallel tests to reduce validation time, and ensure all critical functionality works correctly on every platform your users depend on.
SKILL.md
rendered from the published skill — quoted content, verbatim
Compatibility Testing
Browser engine
Browser-driven checks (viewport emulation, responsive validation, cross-browser screenshots) should go through the qe-browser fleet skill (.claude/skills/qe-browser/). Vibium is installed by aqe init. Quick reference:
```bash
Viewport emulation per breakpoint
vibium viewport 375 667 # mobile vibium viewport 768 1024 # tablet vibium viewport 1920 1080 # desktop
Full device emulation (user-agent, DPR,
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 4 files
.claude/skills/compatibility-testing/SKILL.md
.claude/skills/compatibility-testing/evals/compatibility-testing.yaml
.claude/skills/compatibility-testing/schemas/output.json
.claude/skills/compatibility-testing/scripts/validate-config.json