[Testing] Extension for finding any element & test-7167 fix

[kubaflo]

Scrolling through a list and waiting for a specific element can fail unpredictably due to varying screen sizes and swipe behavior. Instead, I recommend verifying that the list renders correctly after scrolling by checking for the presence of any new element in the array, rather than relying on a specific one.

This PR fixes the failing 7167 test

[dotnet-policy-service]

Hey there @kubaflo! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[kubaflo]

Hi, @anandhan-rajagopal the recently enabled test7167 seems to be failing. What do you think about this change?

[jfversluis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (3)

src/TestUtils/src/UITest.Appium/HelperExtensions.cs:664

• [nitpick] The parameter marked is ambiguous. It should be renamed to elements for clarity.

public static IUIElement WaitForAnyElement(this IApp app, string[] marked, string timeoutMessage = "Timed out waiting for element...", TimeSpan? timeout = null, TimeSpan? retryFrequency = null, TimeSpan? postTimeout = null)

src/TestUtils/src/UITest.Appium/HelperExtensions.cs:666

• [nitpick] The variable result is ambiguous. It should be renamed to queryResult for clarity.

IUIElement result() => FindAnyElement(app, marked);

src/TestUtils/src/UITest.Appium/HelperExtensions.cs:2124

• The error message should be more descriptive. Suggestion: throw new InvalidOperationException($"None of the specified elements were found: {string.Join(", ", elements)}");

throw new InvalidOperationException($"Did not find any elements in the list: {string.Join(", ", elements)}");