-
-
Notifications
You must be signed in to change notification settings - Fork 220
MAUI Android Device Tests #1703
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
Conversation
Hi. I have another big PR with more MAUI stuff coming shortly that includes the deployment flag. But if you can find a way to get device tests going that would be amazing. Currently, I can only write unit tests that run on I think we want to do something like what the MAUI team is doing here: https://github.com/dotnet/maui/tree/main/src/TestUtils Looks like others are trying this as well. See dotnet/maui#3552 (comment) |
Captured this in this issue: #1704 |
b26a87c
to
5e3c730
Compare
I've tried integrating the MAUI TestUtils, as mentioned here dotnet/maui#3552 (comment) and here dotnet/xharness#738 but am getting a lot of errors, such as I assume it has something to do with the imports I had to comment out in the imported projects, but I don't really know how to resolve that... |
Thanks for getting this going! I pushed some changes here that fix the build issues. I also converted tabs to spaces and moved the The tests seems to work when called via xharness:
I didn't try the other targets or wire it to CI, but this is a good start. |
44bb23b
to
5846419
Compare
I've done a couple more fixes to make the
I understand there are AspNetCore-specific utilities in the aspnet maui support tracking issue: dotnet/aspnetcore#35077 |
IMHO, we shouldn't have any ASP.NET Core dependencies in Sentry.Testing at all. That's supposed to be a common project for all test projects to use. I'll split them out. |
Yay, it works! 🎉 |
Integrates MAUI TestUtils, as mentioned in dotnet/maui#3552 (comment) and dotnet/xharness#738
Some tests still fail, see e.g. #1703 (comment) so I've enabled
continue-on-error
for the Android test run and I suggest creating a follow-up issue to resolve these failures.closes #1704
closes #1662
#skip-changelog