-
Notifications
You must be signed in to change notification settings - Fork 537
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[tests] Add Designer Integration Tests to Nightly Tests (#7835)
Context: 618bd4a Commit 618bd4a stated: > Heads-up: xamarin-android/main is *becoming* .NET Android-only; > Classic Xamarin.Android is only supported [through 2024-May-1][0]; > all current and future feature work is oriented toward .NET Android. > Classic Xamarin.Android will only be fully buildable/supportable on > the [d17-5 release branch][1]. This indirectly brings us to the [Xamarin.Android Designer][2] Integration Tests: 1. The Xamarin.Android Designer only works with "Classic" Xamarin.Android; it doesn't work with .NET Android. (It will likely *never* work with .NET Android, unless priorities change.) This is "fine" because Classic Xamarin.Android still works, but 2. *How often* are the Xamarin.Android Designer Integration tests run? (2) is of concern: the Designer Integration tests are normally only run during PR builds and release branch builds. However, the d17-5 release branch is getting very little of either. Meanwhile, the Designer Integration tests live in xamarin/UITools, which is actively developed. This presents a terrible awful no good very bad scenario: UITools changes "something" which breaks the interaction between Xamarin.Android and the Designer, it isn't caught in UITools, and it isn't caught in xamarin-android because the tests in xamarin-android aren't run frequently enough. Address this scenario: add the Designer Integration tests to `azure-pipelines-nightly.yaml`, which will cause them to be run every night. [0]: https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin [1]: https://github.com/xamarin/xamarin-android/commits/d17-5 [2]: https://learn.microsoft.com/en-us/xamarin/android/user-interface/android-designer/
- Loading branch information
1 parent
a200af1
commit 1fae01a
Showing
1 changed file
with
163 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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