a, -all dump all information about Views w, -window=WINDOW dump WINDOW content (default: -1, all windows) k, -do-not-ignore-uiautomator-killed don't ignore UiAutomator killed S, -do-not-start-view-server don't start ViewServer F, -force-view-server-use force view server use (even if UiAutomator present) E, -ignore-version-check ignores ADB version check I, -ignore-secure-device ignore secure device Specifying command line options dump produces a wide variety of info: usage: dump. If you want to list the ID's and some other useful info to incorporate in your tests you can use AndroidViewClient's dump: dumpĪnd produces something like Ī .nexuslauncher:id/scrim_viewĪ .nexuslauncher:id/workspaceĪ .nexuslauncher:id/universal_smartspace_containerĪ .nexuslauncher:id/clock Friday, May 13Ĭom.Ī :id/digital_widgetĪ :id/clock 12:41Ī :id/date FRI, MAY 13Ī .nexuslauncher:id/search_container_all_appsĪ .nexuslauncher:id/mic_icon If not, could you suggest me a good alternative to "uiautomatorviewer"? If there is a simpler alternative allowing to get the strings to pass to the "resourceId" method without using "uiautomatorviewer" and similar softwares, could you suggest me how to do it? I think also Genymotion works in the same way and doesn't allow to inspect apps. I've tried to use the Chrome DevTools but, for what I have understood about it, it doesn't work with native apps but only inspects web pages, correct me if I'm wrong. Are these informations available somewhere on Android Studio? ![]() I've done this technical example because they need something allowing them to know how to find the name of the id and how to find the name of the "package" to use. I've seen this string is formed by what looks like a package (ex. ![]() They need a similar tool because, for example, if they want to catch a specific button and simulate the act of clicking it, for what I have understood until now, they have to call a method called resourceId(String) of UiSelector class, passing in it a string made of an "id", which some elements don't have explicitly declarated in the code, and so that's why they need to be able to debug the running app to see what is, for example, that id of that specific button. To do so, they're using UI Automator, but the "uiautomatorviewer" is causing some problems due to uncovered Java versions (that's what it seemed to me). The developers I'm working with in my team need to make automated integration tests and in some of them need to make actions on particular elements within specific pages of their app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |