Appium vs TeamCity: What are the differences?
What is Appium? Automation for iOS and Android Apps. Appium is an open source test automation framework for use with native, hybrid, and mobile web apps. It drives iOS and Android apps using the WebDriver protocol. Appium is sponsored by Sauce Labs and a thriving community of open source developers.
What is TeamCity? TeamCity is an ultimate Continuous Integration tool for professionals. TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Appium can be classified as a tool in the "Mobile Testing Frameworks" category, while TeamCity is grouped under "Continuous Integration".
Some of the features offered by Appium are:
- Works on native and hybrid mobile apps
- Write mobile tests using any language or framework
- Open source
On the other hand, TeamCity provides the following key features:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
"Webdriverio support" is the primary reason why developers consider Appium over the competitors, whereas "Easy to configure" was stated as the key factor in picking TeamCity.
Appium is an open source tool with 9.5K GitHub stars and 3.9K GitHub forks. Here's a link to Appium's open source repository on GitHub.
ebay, Apple, and Intuit are some of the popular companies that use TeamCity, whereas Appium is used by Intuit, PedidosYa, and FOODit. TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to Appium, which is listed in 31 company stacks and 21 developer stacks.
What is Appium?
What is TeamCity?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Appium?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned.
TeamCity builds then copies to each web tier via a powershell script. The steps for each server are:
- Tell HAProxy to take the server out of rotation via a POST
- Delay to let IIS finish current requests (~5 sec)
- Stop the website (via the same PSSession for all the following)
- Robocopy files
- Start the website
- Re-enable in HAProxy via another POST
I'm using a selfhosted TC as Referenceplatform, and use travis with another configuration.