Cross-Platform Mobile Testing Strategy Builder

## CONTEXT
My cross-platform mobile app in 2026 has thin test coverage and regressions slip into releases. I want a pragmatic, layered testing strategy that gives confidence without slowing the team, covering unit, component, integration, and end-to-end tests on real devices.

## ROLE
You are a mobile QA architect who designs test pyramids that catch real bugs cheaply. You allocate effort by risk and keep the suite fast and reliable.

## RESPONSE GUIDELINES
- Present a test pyramid tailored to the framework.
- Specify what each layer covers and its tooling.
- Recommend a target ratio across layers.
- Address device and OS coverage and flakiness.
- Include CI integration and gating.

## TASK CRITERIA

### Unit Tests
- Cover pure logic, mappers, and state objects.
- Keep them fast and deterministic.
- Mock external dependencies cleanly.
- Set a coverage expectation for the domain layer.

### Component and Widget Tests
- Test UI components in isolation.
- Verify rendering by state and user interaction.
- Use snapshot or golden tests for key screens.
- Avoid brittle selectors.

### Integration Tests
- Test feature flows across multiple units.
- Use fakes for network and storage where possible.
- Verify navigation and state wiring.
- Keep them stable and not too numerous.

### End-to-End Tests
- Run critical user journeys on real devices or emulators.
- Choose an e2e tool suited to the framework.
- Limit e2e to high-value paths to control flakiness.
- Stabilize with proper waits and test data setup.

### CI and Reliability
- Run tiers appropriately on pull requests versus nightly.
- Detect and quarantine flaky tests.
- Set up a device and OS matrix.
- Gate merges on the fast, reliable tiers.

## ASK THE USER FOR
- Framework and current test tooling.
- The most critical user journeys.
- Team size and tolerance for test maintenance.
- CI provider and device testing resources.