-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[Testing] Feature matrix UITest Cases for Entry Control #30033
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
base: main
Are you sure you want to change the base?
[Testing] Feature matrix UITest Cases for Entry Control #30033
Conversation
Hey there @@LogishaSelvarajSF4525! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
/azp run MAUI-UITests-public |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run MAUI-UITests-public |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a full-featured UI test page for the Entry control, exposing its various properties and events through a dedicated feature matrix and options pane.
- Introduces
EntryViewModel
to back all testable Entry properties and events. - Adds
EntryOptionsPage
andEntryControlMainPage
(plus its XAML) to display and interact with Entry features. - Registers the new Entry feature matrix in the core gallery navigation.
Reviewed Changes
Copilot reviewed 5 out of 137 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
EntryViewModel.cs | Implements all bindable properties and event-tracking fields for the Entry control demo. |
EntryOptionsPage.xaml.cs | Provides UI to adjust every Entry property and returns to the main test page. |
EntryControlPage.xaml.cs | Hosts the main Entry feature matrix, binds view model, and hooks up event handlers. |
EntryControlPage.xaml | Defines the layout of the Entry feature matrix, including controls for cursor, selection, events, and navigation. |
CorePageView.cs | Adds the new EntryControlPage to the gallery’s navigation list. |
/azp run MAUI-UITests-public |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run MAUI-UITests-public |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsuarezruiz I have committed this snapshot in the latest changes. |
This PR includes a comprehensive set of UI test cases for the Entry control. The tests validate the Entry control, including properties such as Text, Placeholder, MaxLength, IsPassword, Keyboard, IsReadOnly, IsEnabled, IsVisible, ClearButtonVisibility, HorizontalTextAlignment, VerticalTextAlignment, CursorPosition, SelectionLength, IsSpellCheckEnabled, IsTextPredictionEnabled, ReturnType, ReturnCommand.
Entry Control Feature Matrix
Gallery Page Addition:
GalleryPageFactory
entry for theEntryControlPage
to the navigation structure inCorePageView.cs
. This integrates the new feature matrix page into the test application's navigation.Options Page Implementation:
EntryOptionsPage.xaml
to showcase theEntry
control's features. This page includes aStackLayout
with variousEntry
controls demonstrating properties like Text, Placeholder, MaxLength, IsPassword, Keyboard, IsReadOnly, IsEnabled, IsVisible, ClearButtonVisibility, HorizontalTextAlignment, VerticalTextAlignment, CursorPosition, SelectionLength, IsSpellCheckEnabled, IsTextPredictionEnabled.Main Page Implementation:
EntryControlPage.xaml.cs
, which includes:EntryViewModel
for data binding.Entry
control events (TextChanged
,Focused
,Unfocused
andCompleted
).Issues Identified
Screen.Recording.2025-06-20.at.10.28.03.AM.mov