Flutter

​

Produce a testable build

flutter build apk --release
# APK in build/app/outputs/flutter-apk/app-release.apk

flutter build ios --simulator
# .app in build/ios/iphonesimulator/

​

Upload and run

npm install --save-dev momentic-mobile

npx momentic-mobile assets upload ./build/app/outputs/flutter-apk/app-release.apk \
  --channel dev --tag 1.0.0

fileType: momentic/mobile-test/v2
id: flutter-smoke
platform: android
labels: [smoke]
defaultChannel: dev
defaultTag: "1.0.0"
steps:
  - openApp: com.example.myapp
  - assert: The home screen is visible

npx momentic-mobile run smoke.test.yaml

​

Flutter pitfalls

• Semantics drive what Momentic sees. Momentic reads the native accessibility tree. Flutter renders everything on a canvas, so elements are only visible to the tester when they produce semantics nodes. Most Material and Cupertino widgets do this automatically; custom CustomPainter content and decorative widgets may need Semantics wrappers or excludeSemantics tuning. If a check cannot find a control the user can see, the widget tree is missing semantics.
• Key values do not reach the accessibility tree. ValueKey('login-button') is invisible to Momentic; keys exist for Flutter’s own finder APIs. For a stable hook, wrap the widget in Semantics(label:) or give it a tooltip. Prefer natural-language targets so tests survive renames.
• Splash and async init. A Flutter app often shows a splash while main() awaits. Rather than a fixed wait, assert on the first real screen: assert: The home screen is visible with a timeout.
• DevTools/--dart-define config does not reach the installed binary. Embed test config via --dart-define at build time so the shipped artifact carries it.
• Impeller vs. Skia rendering does not change what the accessibility tree exposes; either engine works.
• WebView content on Android needs WebView.setWebContentsDebuggingEnabled(true).

​

In CI

name: Mobile tests
on: [pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Set up Flutter
        uses: subosito/flutter-action@v2
        with:
          channel: stable

      - name: Build APK
        run: flutter build apk --release

      - name: Upload APK to Momentic
        run: |
          npm install
          npx momentic-mobile assets upload ./build/app/outputs/flutter-apk/app-release.apk \
            --channel dev --tag ${{ github.sha }}
        env:
          MOMENTIC_API_KEY: ${{ secrets.MOMENTIC_API_KEY }}

      - name: Run mobile tests
        run: |
          npx momentic-mobile run --labels smoke \
            --channel dev --tag ${{ github.sha }} -y
        env:
          MOMENTIC_API_KEY: ${{ secrets.MOMENTIC_API_KEY }}

​

Related

• Android app setup
• iOS app setup
• Emulators and simulators