-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 - 3 #25734
[Testing] Enabling ported UITests from Xamarin.UITests to Appium - 3 #25734
Conversation
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. |
/rebase |
b7aa55a
to
4fdd98a
Compare
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
App.WaitForElement("TestReady"); | ||
App.TapBackArrow(); | ||
#if WINDOWS | ||
App.WaitForElement("navViewItem"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsuarezruiz is there a way we can make this work so it doesn't have to be an if/def? Do we need some additional extensions for tabs? Do we need to add some automationids at the platform level?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is taking a few ms to render the tabs and for that reason wait to the parent
x:Name="navViewItem" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anandhan-rajagopal Could you share more details on why you something different in Windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsuarezruiz , In Windows, I'm encountering a timeout exception when using App.WaitForElement("Tab 1"), but using the x:Name for that element has worked successfully.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed Back Button Code!
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 second group of tests enabled.
Additonally the TapBackArrow method is an extension for the IApp interface, designed to facilitate back navigation in an Appium testing context across different platforms. This method checks the type of the app instance and invokes the appropriate back navigation command based on the platform:
Android: Simulates a tap on the navigation button using an XPath query to locate the button by its content description "Navigate up".
Windows, iOS and MacCatalyst: Taps on the "Back" button using an accessibility ID.
TestCases