Then it is parsed and the button in question is located by its name in the sample. Then this file is copied to the working directory C:\Work\. Of course, you could store these to any other location but you will need to adjust it in the code solution.īasically the code gets all elements on the device screen and stores them to a xml file initially on the device itself. The bat files are referred in the project from the folder C:\Work\. Please find attached two archives containing a sample project and two bat files. Since we had faced a similar to that issue the engineering team has prepared a workaround which will be possibly applicable for your scenario as well. Though could you please let me know what concerns you have to share the login credentials with us?Īpart from that I reviewed the scenarios you described and it seems that you are trying to automate dialogs which are not part of the application but are system dialogs. Therefore there is no straight forward action to handle these. I managed to access the shared folder and the application. I will send the login details to can use the below link to download the app couldn't find elements from the dom tree)Ĭan you please let me know why I cannot automate the above 2 scenarios. Select something from the list (this step cannot be automated. Select Create Staff (this step cannot be automated. Select the "Rushdi H&S" App configaration and click done Please see below test step to reproduce it: the interesting thing is, i also couldn't find the elements related to that specific function in the DOM tree. However i found out that, some of the functions in the mobile app cannot be automated the normal way. Real Device-: As you mentioned in the previous email the new elements displaying when refreshed the dome tree. I hope this helps, send us any other question you have and we'll try to help.Īndroid Emulator-: This sorted some of my issues related to android emulator and dom tree issue. Note that you also need to replace the two adb. You can also manually do that if you desire by installing the latest version of the android SDK and manually replacing the adb.exe we use found here: C:\Program Files (x86)\Progress\Test Studio\Bin\MobileStudio\AndroidAdb Use the build that we'll release next week where we have updated the adb.exe to its latest version. Also you'll need to uninstall the app from the emulator using "adb uninstall " The command is "adb.exe install "appName.apk"". apk in the file system and then install in the emulator using the adb command line options. Use the android instrumenation to output the. Try to create a new emulator with latest android. There are a lot things that could go wrong and i can recommend three solutions: From what I see in the screenshot, there is some kind of a version mismatch between the adb.exe and the API level of the android emulator. Unforetuentaly this is a complicated problem because we rely on adb.exe which is the only way we can access android devices and we have no control over its functions. This is my assumption of course, if I'm not correct, can you please send me a screenshot of the exact screen where recording stops working and also a screenshot of the DOM tree that will load when you are on that screen (after you refresh it).ģ. Here the problem is that when you have web elements we go into hybrid test territory and you have to use hybrid android test type. What you need to do is refresh the DOM tree (see problem 1) and a drop down will appear where you can switch between web DOM tree and native DOM tree. I assume that steps are not recorded because you have accessed a screen that contains web elements. Not recording steps is probably connected with problem 1. Here you can see a legend of the different buttons found in the DOM tree UI: DOM tree UI.Ģ. Simply press the refresh button in the DOM tree pane. You probably have noticed that the "out of sync" message appears when you tap some navigation button or load a new menu or something similar. "Out of sync" error in the DOM tree simply means that you have opened a new view in the app and the DOM tree you are seeing in the UI needs to be refreshed in order to see new elements from the new view.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |