[Testing] Fix for flaky test(TwoPaneView_Pane1Priority) in CI #33001
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
dotnet-policy-service
bot
added
the
partner/syncfusion
NafeelaNazhir
added
area-testing
Member
|
/rebase |
github-actions
bot
force-pushed
the
twopaneview_flaky
branch
from
4fccb2e to
fad0744
Compare
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
/rebase |
github-actions
bot
force-pushed
the
twopaneview_flaky
branch
from
fad0744 to
6946a6b
Compare
jfversluis
approved these changes
Dec 17, 2025
github-project-automation
bot
moved this from Ready To Review
to Approved
in MAUI SDK Ongoing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 pull request updates the test order in the
TwoPaneViewFeatureTestsclass. The TwoPaneView_Pane1Priority test was occasionally failing in CI due to RTL state carried over from earlier tests. Setting a clear execution order ensures tests run in the correct sequence and resolves the flaky behavior.