| || |
Opinions on two separate automation frameworks vs single
I am building up a mobile QA division from scratch, this includes setting up an automation framework/infrastructure. I have experience using UI Automation (Apple)/ Illuminator for iOS and Robotium for Android. I am debating setting up a framework that is geared for each respective platform, such as the ones mentioned or setting up a single framework such as Appium. The positives I see for setting up separate frameworks are:
1) Each framework is designed for each platform (i.e., Xcode has test automation built into it, Robotium is designed for Android)
2) If help is needed it is much easier to talk to Dev about their own platform (i.e., will get more help from iOS dev about Xcode/swift vs Appium)
However, I think the idea of one framework (i.e., Appium) is fascinating in the sense of using one API which leads to more code re-use.
What does everything think about this topic? If you have used both systems, which worked better for you? If you have used one system, what was your experience with it?
I'd probably use Appium for the sake of it's popularity and open source community support. I would use 2 separate projects, framework code that's shared I would package in a 3rd package that can be developed independently as a library module. Plus with Appium, you can use 3rd party cloud provider of devices that support the Appium protocol.
Normally I would recommend using tools that use the same language and platform as the tools for the sake of developer support, easier integration with development workflows, and lower costs by borrowing tools and accounts from developers ;-). However, Robotium is pretty hard to work with, it is more intrusive to the AUT. Selenium makes it more user friendly and allows you to use libraries that have been developed by the selenium community for web testing.