TestComplete scalability vs Appium
Hello all,
I'm a long time TestComplete desktop user, but we're developing a companion mobile app for the first time.
I'm in the early stages of researching automation options.
Appium seems to be the industry leader and is supported by many cloud based device farms for scripting, it looks like it can scale to any level needed and do parallel test execution, but the setup is complex and the learning curve is steep.
TestComplete Mobile is tempting as it will allow us to easily write new mobile tests using our existing test framework and knowledge, but I'm concerned about the long term scalability if we want to quickly run tests on multiple devices in the future. At the moment it seems to be limited to just physical connected device(s)?
This will be fine in the short term, but I don't want to get a couple of years into a full implementation, decide we want to do parallel testing on multiple physical/virtual/cloud devices at once, and find out we can't do it.
Does anyone have any experience or comments on the scalability of TestComplete Mobile?
Will it support, or are there plans to support:
a) Multiple physical devices on the same machine.
b) Cloud based device farms.
b) Automated or semi automated device configuration (e.g. deploy the app and run the test). If this can be done with external setup scripts that's OK.
d) Emulators (e.g. launched from Android Studio) - low priority but could be occasionally useful. I'm not as interested in the Chrome simulation capability as it also requires a Web module license which we don't have.
Thanks for any input you may have!
Allen
Hi,
a) In the Object Browser and Object Spy click the 'View more members' link that is above the Properties/Methods tabs. This will provide you with more properties with the chance that you will be able to find those that are stable and unique enough to make it possible to identify the problematic window.
b) It would help to see your code that does not work.
Below assumes that you did not modify Aliases hierarchy and it matches Namemapping one.
.FindChild() method must work, but you must call it for the processQaA360 object and specify search properties for AlertView.
Another option is to enable the Extended Find option for the AlertView object in the Namemapping (this column may be hidden and you should select Field Chooser context menu option to display it) and delete the Window(8) object from Namemapping so that all its child objects move up one level. See https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/extended-search.html for more details.
