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] Enabling some UITests from Issues folder in Appium-7 #27181

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

nivetha-nagalingam
Copy link
Contributor

Description of Change

This PR focuses on enabling and updating 7 testcases in Appium. The tests, previously ignored using Fails attribute, are reviewed, and modified to ensure they are functional with the Appium framework.We are going to enable tests in blocks in different PRs. This is the 7th group of tests enabled.

Test Cases:

  • Issue2680ScrollView
  • Issue6705
  • Issue6945
  • Issue6994
  • Issue7313
  • Issue2674
  • CollectionViewBindingErrorsUITests

@nivetha-nagalingam nivetha-nagalingam added area-testing Unit tests, device tests community ✨ Community Contribution partner/syncfusion Issues / PR's with Syncfusion collaboration labels Jan 16, 2025
@nivetha-nagalingam nivetha-nagalingam marked this pull request as ready for review January 16, 2025 14:24
@nivetha-nagalingam nivetha-nagalingam requested a review from a team as a code owner January 16, 2025 14:24
@jsuarezruiz
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

public void NullPointerExceptionOnFastLabelTextColorChange()
{
App.WaitForElement("Click me");
App.Tap("Click me");
App.WaitForElement("Success");
App.WaitForElement("Success", timeout: TimeSpan.FromSeconds(3));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, why was not necessary on Xamarin.Forms?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We included a timespan because the sample itself displays the success label after a 2-second delay. In Catalyst, we've encountered random failures without the timespan. To address the flakiness in CI, we incorporated the timespan. We have now verified that the WaitForElementTillPageNavigationSettled extension method works successful in locally across all platforms. We have removed the timespan and committed the changes. Could you please review this and share your thoughts?

@jsuarezruiz
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

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.

2 participants