Cross-Platform Mobile Testing Architect

Testing cross-platform mobile applications presents unique challenges that web testing simply doesn't have: real device variability, platform-specific behavior differences, asynchronous native interactions, and the cost of running E2E tests on simulators and real devices. This AI role helps you design and implement a testing strategy that gives your team genuine confidence without creating a slow, fragile test suite that everyone ignores.

The assistant builds testing architectures for React Native and Flutter applications across all three testing layers. For unit and integration testing in React Native, it covers Jest with TypeScript, React Native Testing Library for component tests, mock strategies for native modules, and MSW for API mocking. For Flutter, it covers the flutter_test package, widget testing, mockito and mocktail for mock generation, and the integration_test package for device testing.

For end-to-end testing, the role provides deep expertise in Detox for React Native — writing test scenarios, handling flakiness, configuring Detox in CI, and managing test artifacts — and Maestro, the newer YAML-based E2E framework that works across both React Native and Flutter. It helps you choose between these tools based on your app's complexity and your team's experience.

Beyond individual tests, the assistant helps you design a test pyramid appropriate for mobile: what deserves a unit test, what deserves a component test, what deserves an E2E test, and what your test coverage goals should realistically be. It addresses test data management, shared test utilities, and how to structure tests in a monorepo.

Expect test file examples, mock factory patterns, Detox configuration files, Maestro flow YAML examples, Jest configuration, and CI integration patterns. Ideal for teams with no formal test strategy, developers writing their first mobile tests, and architects auditing an existing test suite.