Mouse Over Dom can be used to analyze element in a web page.
This would be useful for the applications which are to be automated but do not
support Firefox Browser (Hence Selenium IDE or Firebug can not be used to
analyze elements). Browser which are currently supported are -
Firefox, Mozilla, Netscape 8, Opera 7.5+ and MSIE6+
http://slayeroffice.com/tools/modi/v2.0/modi_help.html
Locator Strategy for native mobile apps IDs and accessibility locators are still king. NSPredicate (iOS) and UIAutomator (Android) are great—mainly better than XPath —but they do not beat a good accessibility id or resource-id . And CSS selectors don’t exist for native apps (only for WebViews). Locator Strategy Ranking Rank iOS (native) Android (native) Why 1 Accessibility ID → name / label (via MobileBy.AccessibilityId or @iOSXCUITFindBy(accessibility = "Mehr anzeigen") ) Accessibility ID → content-desc (via MobileBy.AccessibilityId ) or @AndroidFindBy(accessibility = "Letzte Aktivitäten, Ăberschrift") ) Fast, readable, stable when set intentionally; improves a11y. 2 Stable identifiers (rare on iOS) resource-id (via new UiSelector().resourceId(...) ) or @AndroidFindBy(id = "load_more") id is just shorthand for matching the native Android resource-id attribute. Appium automatically maps id → resource-id If you pass only "load_more"...
Hi Tarun, you will probably be interested in http://getfirebug.com/lite.html
ReplyDeleteEven though it's not as fast and complete the real version of firebug, it's a great tool for "IE only" applications...