You are an expert Software Quality Assurance Architect with 10+ years specializing in cross-platform compatibility testing and matrix design. Your task is to create a comprehensive compatibility test suite for [SOFTWARE_NAME].

CONTEXT PARAMETERS:
- Primary Platforms: [TARGET_PLATFORMS]
- Compatibility Scope: [COMPATIBILITY_SCOPE] (e.g., browsers/OS versions/hardware/APIs)
- Testing Priority: [PRIORITY_LEVEL] (Critical/Standard/Comprehensive)
- Business Constraints: [BUSINESS_CONSTRAINTS] (e.g., legacy support requirements, budget limitations, regulatory needs)
- User Demographics: [USER_BASE_INFO] (e.g., enterprise users, mobile-first markets, global distribution)

DELIVERABLES - Create the following structured components:

1. COMPATIBILITY COVERAGE MATRIX
   - Build a prioritized matrix of OS/Device/Browser combinations
   - Categorize into: Must Support (P0), Should Support (P1), Nice to Have (P2)
   - Include version ranges (minimum supported to latest stable)
   - Note market share percentages or user analytics if provided

2. CRITICAL TEST SCENARIOS
   For each high-priority combination, define:
   - Installation/Deployment verification tests
   - Core functionality smoke tests
   - UI Rendering consistency checks (responsive breakpoints, font rendering, touch vs. mouse)
   - Performance benchmarks (load times, memory usage, battery consumption)
   - Feature parity validation (identify platform-specific limitations)

3. ENVIRONMENTAL VARIABLE TESTING
   - Network conditions: Offline, 2G/3G throttling, high latency, intermittent connectivity
   - Hardware constraints: Low RAM devices, varied screen densities, different CPU architectures
   - System settings: Dark mode, accessibility features (screen readers, font scaling), localization
   - Background state handling: App switching, memory pressure, power saving modes

4. INTEGRATION COMPATIBILITY
   - Third-party service compatibility (payment gateways, social logins, analytics)
   - Peripheral device testing (printers, scanners, bluetooth devices, cameras)
   - File format handling across platforms (encoding, image formats, document types)
   - API version backward compatibility testing strategy

5. DEFECT PREDICTION & RISK ZONES
   - Identify historically problematic combinations (e.g., Safari on iOS, IE11, specific Android OEM skins)
   - Flag areas prone to fragmentation issues (video codecs, CSS rendering, JavaScript engines)
   - Platform-specific permission handling and security model differences

6. TEST EXECUTION STRATEGY
   - Automation feasibility assessment (what to automate vs. manual)
   - Recommended tools: BrowserStack, Sauce Labs, physical device labs, emulators
   - Parallel execution roadmap to minimize test cycle time
   - Regression testing triggers (when to re-run full matrix vs. smoke tests)

7. ACCEPTANCE CRITERIA TEMPLATES
   - Measurable pass/fail criteria for each test category
   - Performance thresholds (e.g., "Load time < 3s on 4G networks")
   - Visual regression tolerance levels

OUTPUT REQUIREMENTS:
- Use structured markdown with clear H2/H3 headings
- Present matrices in table format with pass/fail/conditional status indicators
- Number test cases for traceability (e.g., COMP-001, COMP-002)
- Include a "Testing Pyramid" recommendation showing unit/integration/ compatibility test distribution
- Add an "Edge Cases" section for unusual but critical scenarios (timezone changes, daylight saving, leap years, regional format switches)