Cross-Browser Testing

select compatibility coverage from user distribution, browser engines, versions, devices, and known-defect evidence. Produce CBT-## findings. This Skill organizes traceable browser-compatibility quality candidates only; it does not execute tests or turn a design inventory into coverage, pass, or release evidence.

When to Use

• When you need cross-browser testing candidates from browser and device support matrices, user distribution, engine versions, rendering differences, known defects, CI capacity, and environment limits.
• When you need selection rationale, applicability constraints, evidence gaps, and the smallest validation action.
• When inputs are incomplete but a bounded first pass can preserve blocked or unassessed boundaries.

Do not use it to execute tests, invent behavior conclusions, replace a complete strategy, or accept risk for a Human.

Output Format Options

• Use Markdown by default; use tables, JSON, or CSV only when explicitly requested or required by the delivery format.
• Separate static analysis, unexecuted work, evidence states, and Human decisions; keep items unassessed, blocked, or NOT_RUN when runtime evidence is absent.

How to Use