ContributionsMost RecentMost LikesSolutionsXamarin Testing Hey guys, we are about to switch all of our apps to Xamarin and wish to continue UI Testing with TestComplete. However, we experience problems with the Object recognition on Android: Most objects have no id, some have an md5-hash as their id. It was so convenient on Android to have unique ids for most controls and this seems to be gone on Xamarin. Three questions concerning that: What are those md5-hashes based on, when do they change and is there any possibility to still set our own control id? Some objects appear twice with the same id but a different ObjectIndex. I know this phenomenon only from iOS, where the UI is dynamically created during runtime and sometimes UI controls don't get recycled properly so if you reopen the same view again, you might end up with to identical controls, one of them being invisible and the other one being visible. This is a pain in the bum on iOS since it can be quite hard sometimes to determine in TestComplete the instance that is currently visible. My hope is now that we can somehow get rid of that too, but I have no idea how. Screenshot of object ids: (1): md5-hashes, (2) Some objects appear twice Objects are only accessible to a certain level. For instance, we can access and interact with "md52....MasterDetailContainer" but its only child "View("NO_ID")" is inaccessible. TestComplete cannot show a screenshot of it in the ObjectBrowser and any interaction with it (including "Highlight on screen") results in an error. This applies to all of its children, too. This is especially important to solve as all of our UI controls are children of that MasterDetailContainer and having no access to its children renders the tests useless. TestComplete, the Xamarin Forms Designer and the Android UI Automator Viewer show a very different object hierarchy of the same view in the app. How can this be explained? I've been talking to the dev team about all this but as they are new to Xamarin, too, they don't know the answers neither. On the other hand, I know that most of those questions are very specific to Xamarin itself, but I hope to find someone here who has experience with both, Xamarin and TestComplete, to help us out. Greetings, vat Re: Android: Random crashes when using VBScript Hey JNaas, In our company, we use JavaScript as this is the language we (in our company) know the best among the other choices and we had no major problems with the Scripts itself except for our own homemade bugs :) Regards, vat Re: TestComplete ExitCode -805306369 No, our builds run on a dedicated build server, not on the test server as TestComplete needs Windows, iOS apps need Mac OS. Colin_McCrae wrote: Two things that people (especially management) hate happening to automated tests: 1. Crashing. 2. Getting stuck in endless loops. Although I am not part of our management, I don't like that too, which is why I am looking into it right now so please keep calm. Knowing the meaning of the Exit Code helped me a lot in that, so thanks for that :) I think I am going to close this thread as it seems that the actual resolution does not have anything to do anymore with the Exit Code so greetings, vat Re: TestComplete ExitCode -805306369 Hey guys, I just found out why this issue happens. As far as I understood it, TestComplete gets stuck for some reason and TeamCity is waiting for it endlessly and eventually ends up having no more resources in its JVM. Now that "some reason" seems to be a iOS TableViewCell. It takes TestComplete ages to find that cell (I already discussed that issue here) and apparently gets stuck sometimes on that. I'll investigate more tomorrow, until then, have a good night, vat Re: TestComplete ExitCode -805306369 ok, so this explains the exit code but not the actual reason. I guess I will have a look at it and see if th eissue still appears, thanks guys anyway :) Re: TestComplete ExitCode -805306369 Hmm, the TeamCity BuildAgent software is actually designed for months without beeing touched, so I don't see a problem there. Anyway, it was simply waiting for TC since TC simply got stuck somehow. Re: TestComplete ExitCode -805306369 No, usually our tests take 15 Minutes, but I guess that something happened right at the beginning and I simply didn't see it as I did not log in into the CI for 6 days. Re: TestComplete ExitCode -805306369 Our CI is TeamCity, which is Java based, but it runs TestComplete by executing a cmd-Script in the Winows command line, so Java should not matter, in my opinion. Our Application under test is actually a Android App and we use the Visual Studio Emulator for Android to run it. And we use TestComplete 11, latest release btw TestComplete ExitCode -805306369 Hey guys, today, I logged in into our CI and saw that our tests were running since 157 hours (=6 days). So I logged in to the PC running TestComplete and saw that it was basically doing nothing, it opened the ProjectSuite and then nothing happened, it did not run anything. So I clicked on "Stop Test Run" and it saved the log and exited, but the CI told me that the Exit Code was -805306369. Unfortunately, this Exit Code is not documented here. The testlog itself told me that it actually did something, like installing the app and running the tests except that the test device did not show anything of that :) Does anyone know something about that exit code? It would be a great help. Regards, vat SolvedRe: TestComplete Pro licensing question Heyho, anyone from SmartBear reading this? Greetings, vatbub