Re-enabled flaky UI test TextInEditorShouldScroll #29167
Conversation
|
Hey there @@NirmalKumarYuvaraj! 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
the
partner/syncfusion
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| #if MACCATALYST | ||
| App.ScrollDown("editor"); // To make sure the editor is scrolled down | ||
| var yPos = yPosLabel.GetText(); | ||
| Assert.That(yPos,Is.GreaterThan("0")); // The Y position should be greater than 0 after scrolling down |
There was a problem hiding this comment.
Just a note — since this is a UITest, ideally we should verify that scrolling is visually reflected in the UI. Relying on ContentOffset.Y > 0 introduces a logical check, but it doesn’t fully guarantee a visible change occurred on screen.
There was a problem hiding this comment.
@bhavanesh2001 , The test is to check whether the editor is scrollable or not. The previous UI test was flaky because the content was scrolled a pixel off from its original position. So instead of relying on a visual confirmation, I went with an alternative approach. The Y position label text will be updated only if the editor is scrolled. Otherwise it stays as 0.
This is added only to MAC to resolve flaky issue on CI.
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Description of Change
TextInEditorShouldScrollto verify scrolling behavior using ayPositionLabelinstead of relying on screenshot validation. This ensures the test is more deterministic and avoids flakiness in CI, particularly for macOS.Issues Fixed
Fixes #29025