-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run Android tests on background thread #10841
Conversation
Hey there @mattjohnsonpint! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
Also, I presume the same thing is true for iOS tests, but we haven't set that up yet so I didn't want to change that blindly, but it would be here: maui/src/TestUtils/src/DeviceTests.Runners/HeadlessRunner/iOS/MauiTestViewController.cs Lines 29 to 31 in a2947df
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Thanks for this. Once day we will have an actual device test package that shows all the work. |
Just a follow-up. We added iOS tests a few weeks ago, and they have been working well. We didn't need to make any similar change. |
Hi. We have copied the Maui
TestUtils
source code into our project, and use it for running device tests on Android emulators, which we do in our GitHub Actions CI. This has been working well, except that at first we were getting a lot of intermittentkeyDispatchingTimedOut
errors such as the following:(See getsentry/sentry-dotnet#1927)
After some investigation, we realized this was caused because the headless test runner is executing its tests on the main UI thread. We fixed it in our project with getsentry/sentry-dotnet#1929 some time ago - we no longer get
keyDispatchingTimedOut
errors.Since it's been working well for us, I thought I should contribute it back here.