Skip to content

feat(native_views,cli): add desktop preview backend and pn preview #55

feat(native_views,cli): add desktop preview backend and pn preview

feat(native_views,cli): add desktop preview backend and pn preview #55

Workflow file for this run

name: E2E
on:
push:
branches: [main]
pull_request:
branches: [main]
workflow_dispatch:
jobs:
coverage:
# Runs first; fast static check that gates the long device jobs so
# missing demos / flows fail before the emulator boots.
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Check E2E coverage of pythonnative.__all__
run: python scripts/check-e2e-coverage.py
e2e-android:
needs: coverage
runs-on: ubuntu-latest
timeout-minutes: 30
# GitHub-hosted Android emulators grow unstable after ~15 minutes of
# sustained Maestro driving and start reporting "device offline" /
# "device not found" mid-run (the emulator VM, not the app, dies).
# The full 60-flow suite reliably crosses that threshold around the
# ~35th flow. Sharding the run into a few balanced groups — each on
# its own freshly booted emulator — keeps every session well under
# the limit, and parallelizes the Android pass as a bonus. Groups are
# sized so none exceeds ~25 flows; ``components`` is the largest
# single category and runs alone. ``fail-fast: false`` so one shard's
# failure still lets the others report.
strategy:
fail-fast: false
matrix:
include:
- name: components
suites: components
- name: hooks-nav
suites: hooks navigation
- name: layout-styling-anim-misc
suites: layout styling animations misc
name: e2e-android (${{ matrix.name }})
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Set up Java 17
uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: '17'
- name: Install PythonNative
run: pip install -e .
- name: Install Maestro
run: |
curl -Ls "https://get.maestro.mobile.dev" | bash
echo "$HOME/.maestro/bin" >> $GITHUB_PATH
- name: Enable KVM
run: |
echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rules.d/99-kvm4all.rules
sudo udevadm control --reload-rules
sudo udevadm trigger --name-match=kvm
- name: Build, install, and run E2E tests
uses: reactivecircus/android-emulator-runner@v2
with:
api-level: 31
arch: x86_64
script: bash -lc "./scripts/run-e2e.sh android ${{ matrix.suites }}"
e2e-ios:
needs: coverage
runs-on: macos-latest
timeout-minutes: 40
# iOS simulators are stable for the full suite (unlike the Android
# emulator — see the e2e-android note), so this split is purely a
# speed optimization: the iOS Maestro run is ~22 minutes and is the
# critical path for the whole E2E workflow. Sharding it across three
# simulators (same balanced groups as Android) runs them in parallel
# and roughly halves wall-clock time. macOS minutes are free on this
# public repo, so the extra per-shard build/boot overhead is fine.
# ``fail-fast: false`` so one shard's failure still lets the others
# report.
strategy:
fail-fast: false
matrix:
include:
- name: components
suites: components
- name: hooks-nav
suites: hooks navigation
- name: layout-styling-anim-misc
suites: layout styling animations misc
name: e2e-ios (${{ matrix.name }})
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Install PythonNative
run: pip install -e .
- name: Install Maestro and idb
run: |
curl -Ls "https://get.maestro.mobile.dev" | bash
echo "$HOME/.maestro/bin" >> $GITHUB_PATH
brew tap facebook/fb && brew install idb-companion
- name: Build and run E2E tests
run: ./scripts/run-e2e.sh ios ${{ matrix.suites }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}