Add CircleCI job for maestro E2E tests

[ajpallares]

Summary

• Adds two separate CircleCI workflows triggered by the maestro_e2e_tests schedule:
  • maestro-e2e-tests-ios: runs on macOS executor, builds the test app for iOS simulator via flutter build ios --debug --simulator, runs Maestro tests
  • maestro-e2e-tests-android: runs on android:2024.11.1 machine image, creates an Android emulator, builds a debug APK via flutter build apk --debug, runs Maestro tests
• Adds Fastlane lanes with upfront API key validation (UI.user_error! if env var is missing):
  • run_maestro_e2e_tests_ios: replaces API key placeholder, builds with Flutter, installs on simulator, runs Maestro
  • build_maestro_app_android / run_maestro_e2e_tests_android: replaces API key placeholder, builds APK, installs via adb, runs Maestro
• Both lanes use $RC_E2E_TEST_API_KEY_PRODUCTION_TEST_STORE from the e2e-tests CircleCI context
• Test results stored as JUnit artifacts

Depends on #1698

---

Note

Medium Risk
CI pipeline changes add new scheduled iOS/Android emulator runs and Fastlane scripting that mutates the E2E test app at build time; main risk is increased CI flakiness or misconfigured secrets causing failures rather than product impact.

Overview
Adds Maestro end-to-end testing to CircleCI by introducing new run-maestro-e2e-tests-ios and run-maestro-e2e-tests-android jobs that build and run a dedicated Flutter test app on an iOS simulator and an Android emulator, then upload JUnit results as artifacts.

Wires these jobs into the main test workflow (using the e2e-tests context) and also adds dedicated scheduled workflows (maestro_e2e_tests) to run iOS/Android E2E suites independently.

Extends the Fastfile with lanes to build/install the Maestro test app and execute maestro test, including validation of RC_E2E_TEST_API_KEY_PRODUCTION_TEST_STORE and replacing an API-key placeholder before running the suite.

^{Reviewed by Cursor Bugbot for commit b01d19b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b01d19b. Configure here.}

[cursor]

E2E tests unintentionally run on every push/PR

Medium Severity

The run-maestro-e2e-tests-ios and run-maestro-e2e-tests-android jobs are added to the test workflow, which fires on every non-scheduled pipeline trigger (i.e., every push and PR). This means these expensive E2E tests — requiring a macOS m4pro.medium executor and an Android xlarge machine executor — will run on every commit, not just on the maestro_e2e_tests schedule as described in the PR. The dedicated scheduled workflows at lines 666–682 already handle the scheduled runs, making this test-workflow inclusion likely unintentional and costly.

Additional Locations (1)

• .circleci/config.yml#L665-L682

 

^{Reviewed by Cursor Bugbot for commit b01d19b. Configure here.}