[Testing] Feature matrix UITest Cases for IndicatorView Control

[NafeelaNazhir]

This PR includes a comprehensive set of UI test cases for the IndicatorView control. The tests validate the IndicatorView control, including properties such as IndicatorColor, SelectedIndicatorColor, MaximumVisible, Count, Position, HideSingle, IsEnabled, IsVisible, FlowDirection, Shadow, IndicatorTemplate, IndicatorsShape and IndicatorSize

Issues Identified

• IndicatorView.MaximumVisible not respected when IndicatorTemplate is applied #31145
• [iOS, Catalyst] IndicatorView not visible when applying FlowDirection=RightToLeft with IndicatorTemplate #31141
• [iOS, Catalyst] IndicatorView – Applying IndicatorSize with Shadow causes some indicators to be invisible #31140
• IndicatorTemplate in IndicatorView does not update when set dynamically without initial value #31128
• [Android] IndicatorView remains interactive even when IsEnabled="False" #31063
• [iOS, Catalyst] IndicatorView.IndicatorSize does not update dynamically at runtime #31064
• [iOS, Catalyst] IndicatorsShape does not change – always renders as circles #31065
• [iOS] - CarouselView Position and IndicatorView Not Updating When Moving to Next Item in CV2 #29312

Screen.Recording.2025-08-13.at.4.42.20.PM.mov

[dotnet-policy-service]

Hey there @@NafeelaNazhir! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[Copilot]

Pull Request Overview

This PR introduces comprehensive UI test coverage for the IndicatorView control by implementing feature matrix tests that validate various properties and behaviors. The implementation includes visual testing through screenshot verification and property validation through assertions.

Key changes:

• New test infrastructure for IndicatorView with 40 individual test cases covering all major properties
• Platform-specific test exclusions for known issues with proper issue tracking
• Interactive UI components for configuring IndicatorView properties during testing

Reviewed Changes

Copilot reviewed 7 out of 56 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
IndicatorViewFeatureTests.cs	Main test file containing 40 test cases for IndicatorView properties with platform-specific exclusions
IndicatorViewViewModel.cs	ViewModel managing IndicatorView state and carousel data with property change notifications
IndicatorViewOptionsPage.xaml.cs	Code-behind for options configuration page with event handlers for property changes
IndicatorViewOptionsPage.xaml	XAML layout for interactive options configuration with proper AutomationIds
IndicatorViewControlPage.xaml.cs	Main control page code-behind with item management functionality
IndicatorViewControlPage.xaml	Main control page XAML with IndicatorView and CarouselView integration
CorePageView.cs	Registration of the new IndicatorView Feature Matrix in the gallery navigation

---

_{You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[Copilot]

The helper methods IncreasePositionStepper, DecreaseMaximumVisibleStepper, and IncreaseIndicatorSizeStepper contain duplicated platform-specific logic. Consider extracting this into a common method that accepts the stepper automation ID as a parameter.

Suggested change

	App.IncreaseStepper(IndicatorSizeStepper);
	ChangeStepper(PositionStepper, true);
	}
	public void DecreaseMaximumVisibleStepper()
	{
	ChangeStepper(MaximumVisibleStepper, false);
	}
	public void IncreaseIndicatorSizeStepper()
	{
	ChangeStepper(IndicatorSizeStepper, true);
	}
	private void ChangeStepper(string stepperAutomationId, bool increase)
	{
	#if WINDOWS
	if (increase)
	App.IncreaseStepper(stepperAutomationId);
	else
	App.DecreaseStepper(stepperAutomationId);
	#else
	App.WaitForElement(stepperAutomationId);
	if (increase)
	App.IncreaseStepper(stepperAutomationId);
	else
	App.DecreaseStepper(stepperAutomationId);

[NafeelaNazhir]

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

[Copilot]

[nitpick] The large number of AutomationId constants at the top of the class creates maintenance overhead. Consider grouping these constants into a nested static class or using a constants file to improve organization.

Suggested change

	public static class AutomationIds
	{
	public const string Options = "Options";
	public const string Apply = "Apply";
	public const string IndicatorColorBrownButton = "IndicatorColorBrownButton";
	public const string IndicatorColorGreenButton = "IndicatorColorGreenButton";
	public const string SelectedIndicatorColorGrayButton = "SelectedIndicatorColorGrayButton";
	public const string SelectedIndicatorColorOrangeButton = "SelectedIndicatorColorOrangeButton";
	public const string SelectedIndicatorColorPurpleButton = "SelectedIndicatorColorPurpleButton";
	public const string IndicatorShapeSquareRadioButton = "IndicatorShapeSquareRadioButton";
	public const string HideSingleTrueRadioButton = "HideSingleTrueRadioButton";
	public const string HideSingleFalseRadioButton = "HideSingleFalseRadioButton";
	public const string FlowDirectionRightToLeftRadioButton = "FlowDirectionRTLRadioButton";
	public const string IsEnabledFalseRadioButton = "IsEnabledFalseRadioButton";
	public const string IsVisibleFalseRadioButton = "IsVisibleFalseRadioButton";
	public const string PositionEntry = "PositionEntry";
	public const string AddItemButton = "AddItemButton";
	public const string RemoveItemButton = "RemoveItemButton";
	public const string MaximumVisibleStepper = "MaximumVisibleStepper";
	public const string ShadowTrueRadioButton = "ShadowTrueRadioButton";
	public const string CountLabel = "CountLabel";
	public const string PositionLabel = "PositionLabel";
	public const string IndicatorSizeStepper = "IndicatorSizeStepper";
	public const string PositionStepper = "PositionStepper";
	public const string IconTemplateButton = "IconTemplateButton";
	}

[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).