Skip to content

[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

Open
wants to merge 25 commits into
base: main
Choose a base branch
from

Conversation

LogishaSelvarajSF4525
Copy link
Contributor

@LogishaSelvarajSF4525 LogishaSelvarajSF4525 commented Jun 17, 2025

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:

    • Added a new GalleryPageFactory entry for the EntryControlPage to the navigation structure in CorePageView.cs. This integrates the new feature matrix page into the test application's navigation.
  • Options Page Implementation:

    • Created EntryOptionsPage.xaml to showcase the Entry control's features. This page includes a StackLayout with various Entry controls demonstrating properties like Text, Placeholder, MaxLength, IsPassword, Keyboard, IsReadOnly, IsEnabled, IsVisible, ClearButtonVisibility, HorizontalTextAlignment, VerticalTextAlignment, CursorPosition, SelectionLength, IsSpellCheckEnabled, IsTextPredictionEnabled.
  • Main Page Implementation:

    • Added EntryControlPage.xaml.cs, which includes:
      • Initialization of the EntryViewModel for data binding.
      • Event handlers for Entry control events (TextChanged, Focused, Unfocused and Completed).
      • Methods to update cursor position and selection length programmatically.

Issues Identified

Screen.Recording.2025-06-20.at.10.28.03.AM.mov

@dotnet-policy-service dotnet-policy-service bot added the community ✨ Community Contribution label Jun 17, 2025
Copy link
Contributor

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.

@dotnet-policy-service dotnet-policy-service bot added the partner/syncfusion Issues / PR's with Syncfusion collaboration label Jun 17, 2025
@anandhan-rajagopal anandhan-rajagopal added area-testing Unit tests, device tests area-controls-entry Entry labels Jun 17, 2025
@jsuarezruiz
Copy link
Contributor

/azp run MAUI-UITests-public

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jsuarezruiz
Copy link
Contributor

/azp run MAUI-UITests-public

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@LogishaSelvarajSF4525 LogishaSelvarajSF4525 marked this pull request as ready for review June 20, 2025 06:15
@Copilot Copilot AI review requested due to automatic review settings June 20, 2025 06:15
@LogishaSelvarajSF4525 LogishaSelvarajSF4525 requested a review from a team as a code owner June 20, 2025 06:15
Copy link
Contributor

@Copilot Copilot AI left a 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 and EntryControlMainPage (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.

@jsuarezruiz
Copy link
Contributor

/azp run MAUI-UITests-public

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jsuarezruiz
Copy link
Contributor

/azp run MAUI-UITests-public

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@jsuarezruiz jsuarezruiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test VerifyClearButtonVisiblityWhenTextPresentOrEmpty is failing on iOS.
Snapshot different than baseline: ClearButtonVisiblityButton_TextPresent.png (3.79% difference)
image

@LogishaSelvarajSF4525
Copy link
Contributor Author

The test VerifyClearButtonVisiblityWhenTextPresentOrEmpty is failing on iOS. Snapshot different than baseline: ClearButtonVisiblityButton_TextPresent.png (3.79% difference) image

@jsuarezruiz I have committed this snapshot in the latest changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-controls-entry Entry area-testing Unit tests, device tests community ✨ Community Contribution partner/syncfusion Issues / PR's with Syncfusion collaboration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants