What it does
Exercises responsive/mobile-web quality for a feature across a config-driven device/viewport matrix: viewport/layout, touch/interaction, network conditions, and interrupts/state preservation. Emits a Test Execution Report with a device-matrix coverage table, tap-target/text-size results, and a state-preservation tally. Hands native apps to /qa:mobile-automate and payload perf to /qa:perf-test.
When to use it
To cover mobile/responsive quality for a web app.
Prerequisites
qa.config.yml with tooling.mobile_device_matrix, ci.browsers, paths, test_data.*, risk_areas; a Playwright-class runner and emulation.
Output
Test Execution Report (ISO/IEC/IEEE 29119-3 Test Execution Log) under reports_dir, with the device-matrix coverage table; responsive specs as Test Procedures under tests_dir.
Mechanics
How it works
- Read config; resolve the feature/page (default risk_areas.critical when empty)
- Build the device/viewport matrix from config; allocate per risk tier
- Test viewport & layout (no h-scroll, reflow, tap-target size, text legibility)
- Test touch/interaction and network conditions (slow/flaky/offline)
- Test interrupts & state preservation (orientation, background/foreground, resize)
- Implement and run specs across the matrix; route product defects to triage, flake to flaky-hunt
- Emit the device-matrix coverage table, tap-target results, and state-preservation tally
Why it works
The theory behind it
CT-MAT concerns applied to responsive web, exercising the 25010 characteristics most affected by small-screen/touch/network use: compatibility/portability, usability, performance efficiency, reliability.
CT-MAT (Specialist) · ISO/IEC 25010 compatibility / portability / usability / performance efficiency / reliability
Example
See it in use
> /qa:mobile-test "/checkout"✓ Correct when It covers viewports, touch, and network conditions across the device matrix.