Defining the device and browser matrix
We define target coverage from your user analytics. The matrix is refreshed periodically.
We verify that the interface performs to the same standard across every browser and device.
Schedule a meetingWeb UI and mobile testing validates the user interface across different browser, device and operating system combinations. We execute your critical user journeys against your target device matrix and report interface-level findings in priority order.
Interface defects usually appear on a specific device or browser version. Validation carried out in a single environment does not reveal them, and the problem surfaces through user reports instead.
We set the device matrix from your own user data. Scope is built to cover the bulk of your actual usage distribution rather than to try every possible combination.
We define target coverage from your user analytics. The matrix is refreshed periodically.
We prioritise revenue-generating and frequently used journeys. Coverage is ordered by business impact.
We check interface behaviour across different screen sizes and identify the breakpoints where it fails.
We validate iOS and Android applications on real devices. Operating system version coverage is agreed together.
We audit the consistency of interface components across platforms and check them against your brand guidelines.
We plan around your release rhythm, manage the operation and improve it in every cycle.
We define scope, test levels and success criteria against your release calendar. Environment and test data requirements are resolved before the work begins.
We take on team, tool and environment management. Progress is reported regularly against defined KPIs.
We run the tests and prioritise the findings. We track closure together with your development teams.
At the end of every cycle we review scope, automation rate and escaped defect rate. The priorities for the next cycle are set from that review.
We run executions with AutoRunner; cross-browser support and parallel execution let the matrix be covered in a reasonable time. For organisations using RabbitQA, the BrowserHub and MobileHub modules manage browser and device coverage from within a single structure.
Coverage is determined by your user analytics. In most organisations the bulk of usage concentrates in a limited number of combinations. We build the matrix around that distribution and treat the long tail on a risk basis.
Both. Broad coverage scans run in emulated environments while critical journey validation runs on real devices. We use real devices for journeys involving payment and hardware interaction.
They are separate scope items. Mobile web is assessed within the browser matrix, mobile apps within the device and operating system matrix. Both can be covered.
New versions are added to the coverage matrix according to their release calendars. At major version transitions, critical journeys are revalidated as a priority.

Complete the form and we will review your user distribution, your critical journeys and your current test coverage.