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 ported UITests from Xamarin.UITests to Appium - 9 #25815

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

Conversation

anandhan-rajagopal
Copy link
Contributor

Description of Change

This PR focuses on re-enabling and updating following tests from the Xamarin.UITest framework to be compatible with Appium. The tests, previously commented out, 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 9th group of tests enabled.

TestCases

  • Issue1439
  • Issue1939
  • AddingMultipleItemsListView
  • Issue530 (Getting OpenQA.Selenium.InvalidSelectorException on Catalyst, but in manual testing its work fine, so for now we add fails attribute on Catalyst)

@anandhan-rajagopal anandhan-rajagopal marked this pull request as ready for review November 13, 2024 09:14
@dotnet-policy-service dotnet-policy-service bot added the community ✨ Community Contribution label Nov 13, 2024
Copy link
Contributor

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

@anandhan-rajagopal anandhan-rajagopal requested a review from a team as a code owner November 13, 2024 09:14
@jsuarezruiz jsuarezruiz added the area-testing Unit tests, device tests label Nov 13, 2024
@jsuarezruiz
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

App.Tap("Add One");

App.WaitForElement("1234");
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Could include: App.Screenshot("One more element exists");
Is also available in the Appium extension methods.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jsuarezruiz , In this test case, we primarily focused on validating the view presented in the UI. Therefore, we used WaitForElement to ensure that the view is present. According to our understanding, App.Screenshot only captures an image and does not perform any validation. If we still need to include screenshot validations, could we use VerifyScreenshot instead of App.Screenshot?

@@ -1,4 +1,5 @@
using NUnit.Framework;
#if TEST_FAILS_ON_CATALYST // Getting OpenQA.Selenium.InvalidSelectorException on Catalyst
Copy link
Contributor

Choose a reason for hiding this comment

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

On which line?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Encountering an OpenQA.Selenium.InvalidSelectorException on line 23 of Catalyst. We also attempted to adjust the time span for the WaitForElement, still getting same issue.

@jsuarezruiz
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

}

[Test]
public void AddingMultipleListViewTests3AddTwoElementToList()
Copy link
Contributor

Choose a reason for hiding this comment

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

Failing on Android:
image

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants