BrowserStack vs Jenkins: What are the differences?
BrowserStack: Instant access to a lab of 1000+ real mobile and desktop browsers for testing. Live, Web-Based Browser Testing Instant access to all real mobile and desktop browsers. Say goodbye to your lab of devices and virtual machines; Jenkins: An extendable open source continuous integration server. 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.
BrowserStack can be classified as a tool in the "Browser Testing" category, while Jenkins is grouped under "Continuous Integration".
Some of the features offered by BrowserStack are:
- Real Device Cloud. Test on a range of physical Android and iOS mobile devices and tablets for the most accurate results
- 1100+ desktop browsers. Latest versions of IE, Edge, Safari, Chrome, Firefox and more on a range of Windows and OS X platforms on a robust cloud infrastructure
- Test dev environments. Our Local Testing feature allows you to test development and internal websites seamlessly, without setup or configuration
On the other hand, Jenkins provides the following key features:
- Easy installation
- Easy configuration
- Change set support
"Multiple browsers", "Ease of use" and "Real browsers" are the key factors why developers consider BrowserStack; whereas "Hosted internally", "Free open source" and "Great to build, deploy or launch anything async" are the primary reasons why Jenkins is favored.
Jenkins is an open source tool with 13.2K GitHub stars and 5.43K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.
According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to BrowserStack, which is listed in 572 company stacks and 230 developer stacks.
What is BrowserStack?
What is Jenkins?
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 BrowserStack?
Sign up to add, upvote and see more consMake informed product decisions
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
It's incredible how much this service has increased my productivity when it comes to testing new features in multiple browsers. And not only multiple browsers, multiple operating systems as well! And really LOVE that you can run it locally.
We only really need this for IE support
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.
We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.
We use BrowserStack to run end to end tests with Selenium on our dashboard. It runs automatically before every deployment and cancels it if anything is out of place.
BrowserStack is used by our development and support teams during QA and to try and reproduce bugs.
Manually and automatically test our web and mobile apps.