Update on Default Actions
Resolve issues with the 'verify disabled' default action on XPath expressions without a disabled attribute, and fix XPath expression failures for sub-categories in iOS app automation.
Verify Disabled Action Not Working as Expected
Issue: While automating web applications using the Java Selenium framework, the verify disabled default action may not work as intended for every XPath.
Resolution: Use the verify disabled default action only when the XPath of a UI element contains a disabled attribute. Alternatively, use the verify displayed action. When configuring the node, enter the XPath so that it uniquely identifies the disabled element. Use this XPath to check if the element is visible on the page. If the element is visible, you can confirm that the UI element exists on the page.
XPath Expression Failure for Sub-Categories in iOS App Automation
Issue: The XPath expression used to locate and interact with sub-category elements on an iOS app was not working in the Mobile Automation Python Appium framework, causing difficulties in navigating to sub-category pages.
Resolution: Use the tap action to fetch the XPath expression of sub-categories. This adjustment ensures precise selection and navigation to the desired sub-category pages on an iOS app.