[Testing] Feature matrix UITest Cases for FlyoutPage

[NafeelaNazhir]

This pull request adds a comprehensive feature matrix and test UI for the FlyoutPage control in the test host app. It introduces new XAML and code-behind files to demonstrate and test the various properties, behaviors, and navigation scenarios of FlyoutPage, and integrates this new page into the test gallery.

New FlyoutPage feature matrix and test UI:

• Added a new FlyoutControlPage (with code-behind and XAML) that provides an interactive testbed for FlyoutPage features, including dynamic flyout/detail content, property bindings, and navigation scenarios. [1] [2]
• Implemented a detailed options page to configure and test properties like IsVisible, IsPresented, IsEnabled, IsGestureEnabled, FlyoutLayoutBehavior, BackgroundColor, and icon selection for FlyoutPage.

Issues Identified

• [Windows] System.ArgumentException thrown when setting FlyoutLayoutBehavior dynamically #31390
• IsPresented Property in FlyoutPage Not Working Dynamically on Android #31374
• [Windows, Catalyst] IsPresented=true Not Working on Initial Value in FlyoutPage #31372
• Flyout Items Not Displayed in RightToLeft FlowDirection on iOS in Landscape Orientation and Hamburger Icon Positioned Incorrectly #26726
• FlyoutPage's menu icon not showing, when used in a NavigationPage on Android #22116

Screen.Recording.2025-08-29.at.6.53.30.PM.mov

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

The test VerifyFlyoutPage_IsGestureEnabledis failing on Android:

 at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2530
   at UITest.Appium.HelperExtensions.WaitForAtLeastOne(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2547
   at UITest.Appium.HelperExtensions.WaitForElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 743
   at Microsoft.Maui.TestCases.Tests.FlyoutPageFeatureTests.VerifyFlyoutPage_IsGestureEnabled() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/FlyoutPageFeatureTests.cs:line 84
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

[NafeelaNazhir]

The test VerifyFlyoutPage_IsGestureEnabledis failing on Android:

 at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2530
   at UITest.Appium.HelperExtensions.WaitForAtLeastOne(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2547
   at UITest.Appium.HelperExtensions.WaitForElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 743
   at Microsoft.Maui.TestCases.Tests.FlyoutPageFeatureTests.VerifyFlyoutPage_IsGestureEnabled() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/FlyoutPageFeatureTests.cs:line 84
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Hi @jsuarezruiz , I have modified the test case in the latest commit.

[Copilot]

Pull Request Overview

This pull request adds a comprehensive test suite for the FlyoutPage control to the .NET MAUI test infrastructure. It implements a feature matrix testing approach that provides an interactive UI for testing various FlyoutPage properties and behaviors, along with corresponding automated UI tests.

• Adds a feature matrix UI page that demonstrates and tests FlyoutPage functionality with dynamic property configuration
• Implements 22 automated UI tests covering FlyoutPage properties like IsPresented, IsGestureEnabled, FlyoutLayoutBehavior, navigation events, and visual appearance
• Integrates platform-specific test conditions using conditional compilation to handle known issues across different platforms

Reviewed Changes

Copilot reviewed 7 out of 33 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
FlyoutPageFeatureTests.cs	Comprehensive UI test suite with 22 test methods covering FlyoutPage functionality
FlyoutPageViewModel.cs	View model implementing INotifyPropertyChanged for FlyoutPage property binding
FlyoutOptionsPage.xaml.cs	Code-behind for options configuration page with event handlers for property changes
FlyoutOptionsPage.xaml	XAML layout for FlyoutPage property configuration interface
FlyoutControlPage.xaml.cs	Main test page code-behind with FlyoutPage implementation and navigation logic
FlyoutControlPage.xaml	XAML definition of the main FlyoutPage test interface with flyout and detail content
CorePageView.cs	Registration of the new FlyoutPage feature matrix in the test gallery

[Copilot]

The SplitOnPortrait button is placed at Grid.Row="2" Grid.Column="1", but the grid only defines 2 rows (0 and 1). This will cause a layout error as row index 2 doesn't exist.

[NafeelaNazhir]

I have updated the code based on your suggestions in the latest commit.

[Copilot]

[nitpick] Remove excessive blank lines between properties. The empty lines at 46-47 are unnecessary and reduce code readability.

[NafeelaNazhir]

I have updated the code based on your suggestions in the latest commit.

[Copilot]

[nitpick] Remove excessive blank lines before the PropertyChanged event declaration. The empty lines at 140-141 are unnecessary and reduce code readability.

Suggested change

[NafeelaNazhir]

I have updated the code based on your suggestions in the latest commit.

[Copilot]

[nitpick] Remove the blank line before the method declaration. This creates inconsistent spacing compared to other test methods in the class.

Suggested change

[NafeelaNazhir]

I have updated the code based on your suggestions in the latest commit.

[Copilot]

[nitpick] Remove excessive blank lines before the method declaration. The empty lines at 211-212 are unnecessary and create inconsistent spacing.

[NafeelaNazhir]

I have updated the code based on your suggestions in the latest commit.

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

Are covering #31372 in some tests?

[NafeelaNazhir]

Hi @jsuarezruiz , I haven’t included test cases specifically for setting a direct value at initial load. My current coverage focuses on situations where the property is set either through the initial or dynamic value via ViewModel binding.