iOS & Android integration tests #4559
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4559 +/- ##
==========================================
- Coverage 73.50% 73.46% -0.04%
==========================================
Files 482 482
Lines 17678 17678
Branches 3493 3493
==========================================
- Hits 12994 12988 -6
- Misses 3796 3800 +4
- Partials 888 890 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
To make room for Android potentially coming later.
|
@sentry review |
|
Running However, locally everything seems to grind to a halt and the tests don't complete after I'll send a full console log via DM to see if you've got any ideas. |
It should be enough to have the emulator up and running. I suspect something with the host environment because it works for me on both macOS and Linux, and it passes in the CI as well. Could you try applying Android SDK/system image/tool/emulator updates and see if that helps? I suspect there are updates available because you mentioned you don't have Pixel 9 on the list. 🙂
The hang looks random and is not related to any specific change, after all. Might the infamous |
- just pass one test arg - minimize logging (Swift print deadlocks???) - ios: switch from xharness to plain xcrun simctl
Allows running Android integration tests on Windows
To avoid requiring `adb` in `PATH`
Now `pwsh integration-test/android.Tests.ps1` device/emulator discovery works without adb in PATH or ANDROID_SERIAL explicitly defined.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: Stefan Pölz <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
| # by Android Device Tests, or manually when testing locally. This avoids | ||
| # slowing down non-Device Test CI builds further. | ||
| Install-XHarness | ||
| $script:emulator = Get-AndroidEmulatorId |
There was a problem hiding this comment.
TIL about $script scoped variables in PWSH!
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Technically, less correct but doesn't fail even if port forwarding had failed. This way, we can keep it simple and don't need to track it separately.
|
Thanks for testing and helping! |
Co-authored-by: Stefan Pölz <[email protected]> Co-authored-by: James Crosswell <[email protected]>
4 participants
Helps verify that crash events are captured as expected after Cocoa and Java SDK updates (and eventually getsentry/sentry-cocoa#6193):
CrashType.ManagedCrashType.NativeNullReferenceExceptionFor example, see
#skip-changelog
Note
Adds MAUI-based Android and iOS integration tests executed on emulators/simulators in CI, with supporting test app, utilities, and workflow updates (including retries and result artifacts).
integration-test/android.Tests.ps1with retry; checkout submodules; set up Java 17; fetch sharedgithub-workflows; reuse emulator config via YAML anchors; upload bothtest_outputandintegration-test/mobile-app/test_output.integration-test/ios.Tests.ps1with retry; upload both result paths.scriptsin sparse checkout for publishing builds.integration-test/net9-maui/**) targetingnet9.0-android35.0andnet9.0-ios18.0to drive crash scenarios and verify envelopes.integration-test/android.Tests.ps1,integration-test/ios.Tests.ps1; shared helpers inintegration-test/pester.ps1.scripts/device-test-utils.ps1(XHarness install, emulator/simulator helpers);scripts/device-test.ps1now uses these helpers and simplifies simulator selection.integration-test/common.ps1to source shared Pester extensions.Written by Cursor Bugbot for commit 8144e87. This will update automatically on new commits. Configure here.