[Testing] Feature Matrix UITest Cases for DatePicker Control #30159
+1,410
−0
Conversation
This file contains hidden or 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
|
Hey there @@TamilarasanSF4853! 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
bot
added
community ✨
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jsuarezruiz
requested changes
Jun 24, 2025
@jsuarezruiz I have added the pending snapshots in the latest commit. |
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The failed test |
|
/rebase |
github-actions
bot
force-pushed
the
feature-matrix-datepicker
branch
from
ac557ef to
99721fa
Compare
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jsuarezruiz
approved these changes
Jul 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes a comprehensive set of UI test cases for the DatePicker control. The tests validate the DatePicker control, including properties such as Date, Format, FontAttributes, FontFamily, FontSize, IsEnabled, IsVisible, FlowDirection, MinimumDate, MaximumDate, and culture-specific date formatting.
DatePicker Control Implementation:
Added DatePickerControlMainPage to host the DatePicker control, with bindings for properties like Date, Format, FontAttributes, FontFamily, FontSize, IsEnabled, IsVisible, FlowDirection, MinimumDate, and MaximumDate, and event handlers for the DateSelected event.
Created DatePickerOptionsPage to allow users to configure DatePicker properties interactively, including Date, Format, FontAttributes, FontFamily, FontSize, IsEnabled, IsVisible, FlowDirection, MinimumDate, MaximumDate, and culture selection.
Added event handlers for property changes in DatePickerOptionsPage.xaml.cs to update the DatePicker control dynamically through a ViewModel pattern.
Implemented a suite of UI tests in DatePickerFeatureTests to validate property updates, event handling (DateSelected), disabled and visibility states, culture-specific date formatting for various cultures (e.g., en-US, fr-FR, ja-JP, sv-FI), and visual verification of property configurations using VerifyScreenshot() across platforms.
Issues Identified
Screen.Recording.2025-06-24.at.1.50.51.PM.mov