[Testing] Run UI tests with CoreCLR on Android #30842
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This pull request introduces CoreCLR runtime support to the .NET MAUI UI testing infrastructure. The changes enable building and testing MAUI applications using the CoreCLR runtime alongside the existing Mono and NativeAOT variants.
Key changes include:
- Added CoreCLR as a new runtime variant in build and pipeline configurations
- Enhanced UI test pipelines to support CoreCLR-specific build and test stages
- Updated build infrastructure to handle CoreCLR-specific properties and configurations
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
Controls.TestCases.HostApp.csproj |
Added warning suppressions for IL analyzer warnings |
ui-tests.yml |
Updated macOS version and Android API levels for test environments |
ui-tests.yml (common) |
Added CoreCLR build and test stages for Android UI tests |
ui-tests-steps.yml |
Added artifact download step for CoreCLR test samples |
ui-tests-build-sample.yml |
Added CoreCLR-specific artifact publishing conditions |
dotnet.cake |
Implemented CoreCLR runtime variant support and build configuration |
Comments suppressed due to low confidence (1)
src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj:26
- Adding new warning suppressions (IL2026, IL2091, IL2067, IL2072, IL2087, IL3050) without corresponding test cases. These IL analyzer warnings are related to trimming and AOT compatibility. Please ensure there are test cases in TestCases.Shared.Tests that verify the behavior when these warnings would normally be triggered, particularly for CoreCLR scenarios.
<NoWarn>$(NoWarn);CS0618;CS0672;XC0618;XC0022;XC0023;IL2026;IL2091;IL2067;IL2072;IL2087;IL3050</NoWarn>
rmarinho
commented
Jul 25, 2025
rmarinho
commented
Jul 25, 2025
| <WindowsPackageType>None</WindowsPackageType> | ||
| <!-- TODO: remove these obsolete nowarns and fix it in code --> | ||
| <NoWarn>$(NoWarn);CS0618;CS0672;XC0618;XC0022;XC0023</NoWarn> | ||
| <NoWarn>$(NoWarn);CS0618;CS0672;XC0618;XC0022;XC0023;IL2026;IL2091;IL2067;IL2072;IL2087;IL3050</NoWarn> |
There was a problem hiding this comment.
Since this was not running with NAtiveAOT it was throwing the errors.
|
/rebase |
github-actions
bot
force-pushed
the
fix-30278
branch
from
be931e9 to
da836c4
Compare
|
/rebase |
github-actions
bot
force-pushed
the
fix-30278
branch
from
da836c4 to
fd905c3
Compare
|
/rebase |
simonrozsival
approved these changes
Aug 18, 2025
github-project-automation
bot
moved this from Ready To Review
to Done
in MAUI SDK Ongoing
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Add UITests stage for using CoreCLR, enable NativeAOT for UITEsts.
This pull request introduces support for the CoreCLR runtime variant, refactors build and test scripts for better maintainability, and updates the pipeline configurations. The most significant changes include adding CoreCLR as a runtime option, enhancing build tasks to accommodate the new runtime, and updating pipeline files to support CoreCLR-specific builds and tests.
Seems we weren't actually build also the NativeAOT uitest step correctly, so fixing that too on this PR.
CoreCLR Runtime Support:
CoreCLRas a new runtime variant in theRuntimeVariantenum and introduced a corresponding flagUSE_CORECLRineng/cake/dotnet.cake.Task("uitests-apphost")to include CoreCLR-specific build properties, such asUseMonoRuntimeandTargetFramework.Build Script Refactoring:
DefaultDotnetVersionto support dynamic target framework versions via arguments or environment variables.dotnet,dotnet-local-workloads, anddotnet-samples. [1] [2] [3]GenerateCgManifesttask andRunTestWithLocalDotNetmethod. [1] [2]Pipeline Updates:
ui-tests-build-sample.ymlto include CoreCLR as a runtime variant and added conditions for publishing CoreCLR-specific artifacts. [1] [2]ui-tests.ymlfor both build and test workflows. [1] [2]macOS-15and Android API levels to36inui-tests.yml. [1] [2]Project Configuration:
IL2026,IL2091, etc.) in theControls.TestCases.HostApp.csprojfile to address compatibility issues.Issues Fixed
Fixes #30278