mobile-testing
/mobile-testing
Opisuje wzorce testów E2E aplikacji mobilnych: Flutter integration_test, Patrol, Maestro, testy golden, macierz urządzeń i zarządzanie danymi testowymi.
- Autor
- irahardianto ↗
- Repozytorium
- awesome-agv ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 15.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 15.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Opisuje wzorce testów E2E aplikacji mobilnych: Flutter integration_test, Patrol, Maestro, testy golden, macierz urządzeń i zarządzanie danymi testowymi.
Oryginalny opis (EN)
Mobile E2E testing patterns — Flutter integration_test, Patrol, Maestro, golden testing, device matrix, and test data management. Use when writing E2E tests for mobile applications.
Jak działa
- Overview
- Screen Object Model
- Test Data Management
- Device Matrix Testing
- Offline & Network Testing
- CI Configuration
- Framework Selection Guide
Podgląd SKILL.md
---
name: mobile-testing
description: >-
Mobile E2E testing patterns — Flutter integration_test, Patrol, Maestro,
golden testing, device matrix, and test data management.
Use when writing E2E tests for mobile applications.
---
# Mobile Testing
## Overview
Load this skill when writing E2E or integration tests for mobile applications (Flutter, React Native, or native iOS/Android). This skill complements the `browser-automation` skill which covers web — this skill covers native mobile.
**Framework references:** This file covers patterns and strategies. For framework-specific setup, API, and code examples, see:
- [Flutter (integration_test, Patrol, Golden Testing)](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/flutter.md)
- [Maestro (cross-platform YAML flows)](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/maestro.md)
## Screen Object Model
The mobile equivalent of Page Object Model. Encapsulates screen-specific finders, interactions, and assertions in reusable classes.
### Principles
- **One class per screen** — mirrors the app's navigation structure
- **Encapsulate finders** — expose semantic methods, not raw selectors
- **Compose flows** — tests chain screen objects into user journeys
- **Assert at the screen level** — each screen knows its own success/error states
### Structure
```
integration_test/
screens/
login_screen.dart # Finders + interactions for login
home_screen.dart # Finders + interactions for home
checkout_screen.dart # Finders + interactions for checkout
flows/
purchase_flow_test.dart # Composes screen objects into journey
```
### Pattern (language-agnostic)
Each screen object exposes:
1. **Finders** — locators for key UI elements (by key, type, text, accessibility ID)
2. **Interactions** — methods for user actions (`enterEmail()`, `tapLogin()`, `scrollToItem()`)
3. **Composed actions** — higher-level methods combining multiple interactions (`loginAs(email, password)`)
4. **Assertions** — methods to verify screen state (`assertErrorVisible()`, `assertWelcomeShown()`)
For framework-specific implementations, see the references:
- **Flutter/Patrol:** See [flutter.md § Screen Object Model](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/flutter.md)
- **Maestro:** Uses YAML sub-flows rather than code classes — see [maestro.md](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/maestro.md)
## Test Data Management
### API Seeding
Call backend API to create test state before tests run:
- Create test users with specific roles/permissions
- Seed catalog/inventory data
- Set up payment test scenarios (test cards, etc.)
**Pattern:** Create a `TestApi` helper class that wraps seeding endpoints. Inject the base URL via environment configuration.
### State Reset
- Reset between tests to ensure isolation — call a cleanup endpoint or use database rollback
- Use `setUp()`/`tearDown()` (or framework equivalent) to automate reset
- Never rely on test execution order
### Environment Configuration
- Use build-time environment variables to switch between local and staging backends
- Keep test API keys separate from production keys
- Example: `BASE_URL` and `API_KEY` injected via `--dart-define` (Flutter) or `.env` (React Native)
### Test Fixtures
- Create factory functions for common test data (test users, orders, products)
- Prefer deterministic data over random — random data makes failures hard to reproduce
- Use unique identifiers per test run to avoid cross-test contamination
## Device Matrix Testing
### Screen Sizes to Cover
| Category | Example | Resolution |
|----------|---------|------------|
| Small phone | iPhone SE | 375×667 |
| Medium phone | iPhone 14 | 390×844 |
| Large phone | iPhone 14 Pro Max | 430×932 |
| Tablet | iPad Air | 820×1180 |
| Foldable | Galaxy Fold (open) | 717×512 |
### Testing Strategy
- **P0 tests:** Run on medium phone (most common) — minimum viable matrix
- **P1 tests:** Add small phone + tablet — catch responsive layout breakpoints
- **P2 tests:** Add foldable + landscape orientation — catch edge layout issues
- **Platform differences:** Test on both iOS and Android when behavior diverges (navigation style, permissions UX, keyboard behavior)
### Orientation Testing
- Test portrait (default) and landscape for screens that should support rotation
- Verify layout adapts correctly — no overflow, no clipped content
- Some screens should lock orientation — verify rotation is ignored
For framework-specific size simulation APIs, see the [Flutter reference](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/flutter.md).
## Offline & Network Testing
### Patterns to Test
1. **Offline detection** — app shows offline banner or indicator
2. **Offline-first operations** — user can perform actions that queue locally
3. **Reconnection sync** — queued operations sync when connection restores
4. **Graceful degradation** — app disables features requiring network with clear UX
5. **Slow network** — loading states appear, no premature timeouts, no duplicate submissions
### Testing Approach
- **Mock HTTP client:** Inject a client that throws network errors — test offline UI states without device manipulation
- **Patrol native interactions:** Use `$.native.disableWifi()` / `$.native.enableWifi()` for real airplane mode testing on physical devices or emulators
- **Android emulator flags:** Use `-netdelay` and `-netspeed` flags for slow network simulation
For code examples, see the [Flutter reference](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/flutter.md).
## CI Configuration
### Key Considerations
- **Android emulator in CI:** Requires KVM hardware acceleration on Linux runners. Use `reactivecircus/android-emulator-runner` GitHub Action.
- **iOS simulator in CI:** Requires macOS runners. Create and boot simulator via `xcrun simctl`.
- **Parallel execution:** Split test files across CI matrix jobs for faster runs.
- **Artifact collection:** Always upload screenshots and device logs on failure (`actions/upload-artifact`).
- **Golden tests:** Generate golden files locally, commit to repo, compare in CI. Set tolerance for cross-platform rendering differences.
For CI workflow YAML examples, see the [Flutter reference § CI Configuration](file:///home/irahardianto/works/projects/awesome-agv/.agents/skills/mobile-testing/references/flutter.md).
## Framework Selection Guide
| Stack | Recommended Framework | Native Interactions | Visual Regression |
|-------|----------------------|--------------------|--------------------|
| **Flutter** | `integration_test` + Patrol | Patrol | `golden_toolkit` |
| **React Native** | Detox or Maestro | Maestro | Screenshot comparison |
| **Native iOS** | XCUITest or Maestro | XCUITest / Maestro | Snapshot testing |
| **Native Android** | Espresso or Maestro | Espresso / Maestro | Screenshot testing |
| **Cross-platform** | Maestro | Maestro | Maestro screenshots |
Pliki w paczce (3)
- SKILL.md 7 KB
- references/flutter.md 11 KB
- references/maestro.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · irahardianto/awesome-agv | 100 | MIT |
| proffesor-for-testing/agentic-qe | 100 | MIT |
| mhmdelgazzar/agentex | 100 | MIT |
| thedaviddias/front-end-checklist | 100 | MIT |
| arozumenko/sdlc-skills | 91 | MIT |
| j4flmao/agent-skills | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 9fcddf0a77d2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100patrol-migrate-from-maestro
Przenosi przepływy testów Fluttera z Maestro do testów end-to-end w Patrol, zamieniając selektory na klucze widgetów. - 100flutter-testing
Planuje strategię testów Flutter: fałszywki i mocki, testy golden, testy E2E z Patrol oraz niestabilne testy w CI. - 100patrol-write-test
Pisze testy end-to-end Patrol dla aplikacji Flutter: kolejność akcji, reguły API i asercji, obsługa natywnych okien dialogowych i konwencje kluczy widżetów. - 100flutter-testing
Pisze testy jednostkowe, widgetów i integracyjne we Flutterze ze wzorcem robotów, kluczami widgetów i Patrol. - 90agency-mobile-test-setup
Konfiguruje testy mobilne E2E: deterministyczne smoke w CI przez Maestro oraz agentowe testy QA przez agent-device. - 100mobile-app-testing
Prowadzi testowanie aplikacji mobilnych: testy jednostkowe, automatyzację UI i testy wydajności, infrastrukturę testową, E2E, farmy urządzeń oraz niestabilne testy.