Appium vs Jenkins

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Appium

Stacks650

Followers574

Votes28

GitHub Stars20.8K

Forks6.2K

Appium vs Jenkins: What are the differences?

Introduction

Appium and Jenkins are both tools commonly used in the field of software development and testing. However, there are several key differences between the two.

Programming Language Support: Appium supports a wide range of programming languages such as Java, Python, Ruby, and C#, allowing developers to write their automation test scripts in their preferred language. On the other hand, Jenkins does not have direct programming language support but provides integration with various development tools and languages.
Mobile Application Testing vs Continuous Integration: Appium is primarily used for mobile application testing, providing a framework for automating mobile apps on multiple platforms such as iOS and Android. Jenkins, on the other hand, is a continuous integration and continuous delivery tool used for building, testing, and deploying software projects.
User Interface: Appium focuses on providing a user-friendly graphical interface for easy test case creation and execution. It allows test scripts to be written in a user-readable format, making it more accessible for non-technical testers. Jenkins, on the other hand, is more command-line oriented and primarily used by developers and DevOps professionals, offering a web-based user interface with extensive configuration options.
Integration and Plug-ins: Jenkins has a vast selection of plugins available for integration with various tools and technologies, allowing customizations and extending its functionalities. Appium, although it provides some integration options, has a more limited range of plugins and integrations compared to Jenkins.
Scalability and Distributed Testing: Appium supports parallel testing on multiple devices or simulators, allowing for faster execution and scalability. Jenkins, on the other hand, supports distributed testing by distributing test jobs to multiple agents, enabling simultaneous testing on different machines.
Focus and Purpose: Appium's main focus is on mobile app testing, providing cross-platform support and automating UI interactions. Jenkins, on the other hand, is primarily used for continuous integration and delivery, focusing on building and deploying software projects.

In Summary, Appium is a tool for automating mobile app testing with support for multiple programming languages and a user-friendly interface, while Jenkins is a continuous integration and delivery tool focused on building and deploying software projects with extensive plugin support and scalability options.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Jenkins, Appium

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k

Comments

Detailed Comparison

Jenkins	Appium
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.	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.
Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support	Works on native and hybrid mobile apps; Write mobile tests using any language or framework; Open source; Facilitates mobile continuous integration; Mobile test automation tool; Cross-platform (iOS, Android); Framework based on Selenium
Statistics
GitHub Stars 24.6K	GitHub Stars 20.8K
GitHub Forks 9.2K	GitHub Forks 6.2K
Stacks 59.2K	Stacks 650
Followers 50.4K	Followers 574
Votes 2.2K	Votes 28
Pros & Cons
Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Lack of support 7 Limited abilities with declarative pipelines	Pros 12 Webdriverio support 6 Java, C#, Python support 3 Open source 2 Great GUI with inspector 2 Active community
Integrations
No integrations available	Sauce Labs

What are some alternatives to Jenkins, Appium?

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

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.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

Appium vs Jenkins: What are the differences?

Introduction

Appium and Jenkins are both tools commonly used in the field of software development and testing. However, there are several key differences between the two.

Programming Language Support: Appium supports a wide range of programming languages such as Java, Python, Ruby, and C#, allowing developers to write their automation test scripts in their preferred language. On the other hand, Jenkins does not have direct programming language support but provides integration with various development tools and languages.
Mobile Application Testing vs Continuous Integration: Appium is primarily used for mobile application testing, providing a framework for automating mobile apps on multiple platforms such as iOS and Android. Jenkins, on the other hand, is a continuous integration and continuous delivery tool used for building, testing, and deploying software projects.
User Interface: Appium focuses on providing a user-friendly graphical interface for easy test case creation and execution. It allows test scripts to be written in a user-readable format, making it more accessible for non-technical testers. Jenkins, on the other hand, is more command-line oriented and primarily used by developers and DevOps professionals, offering a web-based user interface with extensive configuration options.
Integration and Plug-ins: Jenkins has a vast selection of plugins available for integration with various tools and technologies, allowing customizations and extending its functionalities. Appium, although it provides some integration options, has a more limited range of plugins and integrations compared to Jenkins.
Scalability and Distributed Testing: Appium supports parallel testing on multiple devices or simulators, allowing for faster execution and scalability. Jenkins, on the other hand, supports distributed testing by distributing test jobs to multiple agents, enabling simultaneous testing on different machines.
Focus and Purpose: Appium's main focus is on mobile app testing, providing cross-platform support and automating UI interactions. Jenkins, on the other hand, is primarily used for continuous integration and delivery, focusing on building and deploying software projects.

Appium vs Jenkins

Overview