Skip to content
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

[Testing] Enable Catalyst UI Tests with Screenshot Verification - 2 #26874

Merged

Conversation

anandhan-rajagopal
Copy link
Contributor

Description

This PRs adds UI Tests to the Catalyst Platform, featuring screenshot verification to improve our testing capabilities. This enhancement will aid in maintaining visual consistency and detecting any unexpected changes in the Catalyst UI. Previously, our UI tests for Catalyst lacked screenshot validation, so we ignored the tests on Catalyst. Here we enabled UITests for the bug fixes we’ve previously addressed.

@anandhan-rajagopal anandhan-rajagopal requested a review from a team as a code owner December 31, 2024 01:36
@dotnet-policy-service dotnet-policy-service bot added the community ✨ Community Contribution label Dec 31, 2024
@anandhan-rajagopal anandhan-rajagopal added partner/syncfusion Issues / PR's with Syncfusion collaboration area-testing Unit tests, device tests labels Dec 31, 2024
@jfversluis
Copy link
Member

jfversluis commented Dec 31, 2024

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@jfversluis jfversluis added this to the .NET 9 SR3 milestone Jan 1, 2025
@jfversluis jfversluis merged commit 46096ff into dotnet:main Jan 1, 2025
104 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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