qa-compatibility
Browser + OS compatibility testing: 5 skills (browser-matrix-runner, browser-matrix-strategy-reference, compatibility-budget, os-matrix-runner, selenium-grid-4-runner) and 1 agent (compatibility-matrix-auditor).
Install this plugin
/plugin install qa-compatibility@testland-qaPart of role bundles: qa-role-manual-tester, qa-role-automation-engineer, qa-role-sdet, qa-role-frontend, qa-role-mobile-desktop
qa-compatibility
Browser and OS compatibility testing - runs the smoke suite across configured browser/OS matrices, with budget conventions for choosing which combinations to test.
Components
| Type | Name | Description |
|---|---|---|
| Skill | browser-matrix-runner | Configures a CI matrix that runs the smoke / regression suite across multiple browsers per Playwright's three-engine support (Chromium, F... |
| Skill | browser-matrix-strategy-reference | Pure-reference catalog for designing a browser / OS / device test matrix. |
| Skill | compatibility-budget | Pure-reference for choosing the compatibility matrix - defines tier-1 (must work; covered per-PR) vs tier-2 (must work; covered nightly)... |
| Skill | os-matrix-runner | Configures a CI matrix that runs tests across operating systems (Linux / macOS / Windows) and runtime versions (Node 18/20/22; Python 3.1... |
| Skill | selenium-grid-4-runner | Author and operate Selenium Grid 4 - self-hosted distributed WebDriver. |
| Agent | compatibility-matrix-auditor | Adversarial auditor that reads an existing browser/OS support matrix and checks it against the plugin's T1/T2/T3 tier conventions and bud... |
Install
/plugin marketplace add testland/qa
/plugin install qa-compatibility@testland-qaSkills
browser-matrix-runner
Configures a CI matrix that runs the smoke / regression suite across multiple browsers per Playwright's three-engine support (Chromium, Firefox, WebKit) plus branded variants (chrome, msedge channels). Wires GitHub Actions / GitLab CI matrix syntax, captures per-browser screenshots, and aggregates per-browser pass/fail. Use when the product targets multiple browsers and the team wants automated cross-browser regression.
browser-matrix-strategy-reference
Pure-reference for designing and reviewing a browser / OS / device test matrix from traffic data. Covers the T1/T2/T3 tier-membership heuristics (T1 currently >=5% of traffic, T2 1-5% or statutory, T3 <1% but with customer demand), the traffic-share data sources (own analytics, StatCounter, MDN browser-compat-data), a worked B2B SaaS matrix template with a tier-change log for audit trails, the cost-tier infrastructure mapping (bundled engine vs cloud grid vs real device), and how to justify dropping a legacy browser (IE11, old Safari iOS). Use when designing an initial browser matrix, running a quarterly re-tier review, or building the case to drop a browser. Distinct from compatibility-budget (multi-product-type budgets and the external 'what we support' statement) and compatibility-matrix-auditor (audits a committed matrix for violations).
compatibility-budget
Pure-reference for choosing the compatibility matrix - defines tier-1 (must work; covered per-PR) vs tier-2 (must work; covered nightly) vs tier-3 (should work; covered pre-release) vs unsupported (explicitly out of scope). Includes example budgets per product type (web / desktop / mobile / library), the matrix-size cost / coverage trade-off, and templates for documenting "what we support" externally. Use when a team needs to decide which browser / OS / runtime combinations to commit to.
os-matrix-runner
Configures a CI matrix that runs tests across operating systems (Linux / macOS / Windows) and runtime versions (Node 18/20/22; Python 3.10/3.11/3.12; Java 17/21; .NET 6/8). Wires GitHub Actions matrix syntax, addresses OS-specific quirks (path separators, line endings, file permissions). Use when the product ships across OS / runtime combinations and the team needs continuous cross-platform coverage.
selenium-grid-4-runner
Author and operate Selenium Grid 4 - self-hosted distributed WebDriver. Covers the six-component architecture (Router / Distributor / Session Map / Event Bus / New Session Queue / Node), standalone vs hub-and-node deployment modes, Docker-image stack (selenium/standalone-chrome, selenium/hub, selenium/node-chrome), node registration, session-queue tuning, and observability. Use for self-hosted cross-browser testing - alternative to cloud grids (BrowserStack / Sauce Labs / LambdaTest) when data residency or cost-control require an on-prem solution.