Need advice about which tool to choose?Ask the StackShare community!

BrowserStack

2.6K
1.9K
+ 1
430
Cypress

1.3K
1.5K
+ 1
102
Add tool

BrowserStack vs Cypress: 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; Cypress: Better, faster, and more reliable testing for anything that runs in a browser. Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.

BrowserStack can be classified as a tool in the "Browser Testing" category, while Cypress is grouped under "Javascript Testing Framework".

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, Cypress provides the following key features:

  • Time Travel
  • Debuggability
  • Automatic Waiting

"Multiple browsers" is the primary reason why developers consider BrowserStack over the competitors, whereas "Open source" was stated as the key factor in picking Cypress.

According to the StackShare community, BrowserStack has a broader approval, being mentioned in 579 company stacks & 239 developers stacks; compared to Cypress, which is listed in 60 company stacks and 45 developer stacks.

Advice on BrowserStack and Cypress

I am looking to purchase one of these tools for Mobile testing for my team. It should support Native, hybrid, and responsive app testing. It should also feature debugging, parallel execution, automation testing/easy integration with automation testing tools like Selenium, and the capability to provide availability of devices specifically for us to use at any time with good speed of performing all these activities.

I have already used Perfecto mobile, and Sauce Labs in my other projects before. I want to know how different or better is AWS Device farm in usage and how advantageous it would be for us to use it over other mentioned tools

See more
Replies (2)
Recommends
BrowserStackBrowserStack

Stability - Just works. Availability - More than 15 datacenters. Enterprise features like SSO, local testing and SOC2/GDPR compliant.

See more
Jaymie Falconi
Recommends
BitBarBitBar

BitBar's Dedicated Devices would be a great option for you. It allows you to dedicate (reserve) devices for your use only which also having access to all of the devices in the shared cloud. BitBar has the features and integrations that you are looking for as well.

See more
Yildiz Dila
testmanager/automation tester at medicalservice | 5 upvotes 路 147.7K views
Needs advice
on
ProtractorProtractor
and
CypressCypress

In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...

See more
Replies (2)
Kevin Emery
QE Systems Engineer at Discovery, Inc. | 3 upvotes 路 66.5K views

I've used both Protractor and Cypress extensively. Cypress is the easier and more reliable tool, whereas Protractor is the more powerful tool. Your choice of tool should depend on your specific testing needs. Here are some advantages and disadvantages of each tool:

Cypress advantages:

  • Faster

  • More reliable (tends to throw fewer intermittent false failures)

  • Easier to read code (handles promises gracefully)

Cypress disadvantages:

  • Cannot switch between browser tabs

  • Cannot switch to iFrames

  • Cannot specify clicks or keypresses explicitly as if a real user was interacting

  • Cannot move the mouse to specific co-ordinates

  • Sometimes has trouble switching between different top-level domains, so not good for testing external links

  • Cypress is a newer tool with less extensive documentation and less community support

Protractor advantages:

  • More powerful because it is Selenium-based - it can switch between tabs, it can handle external links to other domains, it can handle iFrames, simulate keypresses and clicks, and move the mouse to specific co-ordinates within the browser.

  • More extensive community support and documentation

Protractor disadvantages:

  • Slower and more brittle - in general there is a higher likelihood of cryptic and/or intermittent errors which may cause your tests to fail even though there is nothing wrong with your application

  • For highly experienced automation engineers, the fundamental "brittle" nature of Selenium can be worked around - it can be reliable but only if you really know what you are doing

  • Less graceful handling of promises - relies on async/await or .then to manage the order of execution. Therefore it is a bit harder to read the code.

  • Harder to set up, and the method of setup impacts its reliability. For example, a hub/node configuration where the selenium jar is on a different physical machine than the browser under test will cause unreliability in your tests. Not everyone knows about this type of thing, so it's common to find Selenium frameworks that are set up poorly.

It's probably better to use Cypress if

  • you're at a smaller company and have a close relationship with developers who can help write hooks or stubs in their code to assist your testing

  • you don't need to do things like switch between tabs or test links to external top-level domains

It's probably better to use Protractor if

  • You might need to switch between tabs or test external links to other domains within the scope of your framework

  • You want to use a more accurate simulation of how a real user interacts with a browser (i.e. click at this location, type these keys)

  • You're at a company where you won't have any support from developers in writing hooks or stubs to make their code more testable in a less powerful framework like Cypress

See more
Jian Wang
Web Engineer at sentaca | 1 upvotes 路 95.3K views
Recommends

Please try Handow, the e2e tool basing on Puppeteer.

Gherkin syntax compatible

Chrome/Chromium orentied, driven by Puppeteer engine

Complete JavaScript programming

Create test suites rapidly without coding (or a little bit), basing on built-in steps library

Schedule test with plans and arrange stories with sequential stages

Fast running, execute story groups in parallel by multi-workers

Built-in single page report render

Cover page view, REST API and cookies test

https://github.com/newlifewj/handow

http://demo.shm.handow.org/reports

See more
Decisions about BrowserStack and Cypress
Shared insights
on
JestJestCypressCypress

As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of BrowserStack
Pros of Cypress
  • 130
    Multiple browsers
  • 71
    Ease of use
  • 59
    Real browsers
  • 40
    Ability to use it locally
  • 22
    Good price
  • 17
    Great web interface
  • 15
    IE support
  • 13
    Official mobile emulators
  • 12
    Cloud-based access
  • 11
    Instant access
  • 7
    Real mobile devices
  • 5
    Multiple Desktop OS
  • 4
    Screenshots
  • 4
    Can be used for Testing and E2E
  • 4
    Selenium compatible
  • 3
    Pre-installed developer tools
  • 3
    Video of test runs
  • 2
    Favourites
  • 2
    Webdriver compatible
  • 2
    Supports Manual, Functional and Visual Diff Testing
  • 2
    Many browsers
  • 1
    Free for Open Source
  • 1
    Cypress Compatible
  • 25
    Open source
  • 19
    Great documentation
  • 17
    Fast
  • 16
    Simple usage
  • 10
    Cross Browser testing
  • 9
    Easy us with CI
  • 4
    Npm install cypress only
  • 1
    Good for beginner automation engineers

Sign up to add or upvote prosMake informed product decisions

Cons of BrowserStack
Cons of Cypress
  • 1
    Very limited choice of minor versions
  • 19
    Cypress is weak at cross-browser testing
  • 12
    Switch tabs : Cypress can'nt support
  • 11
    No iFrame support
  • 8
    No file upload support
  • 8
    No xPath support
  • 8
    No multiple domain support
  • 8
    No page object support
  • 7
    Re-run failed tests retries not supported yet
  • 7
    Cypress doesn't support native app
  • 7
    No support for multiple tab control
  • 6
    No support for multiple browser control
  • 6
    No support for Safari
  • 4
    $20/user/thread for reports
  • 4
    Not freeware
  • 4
    Adobe
  • 3
    No 'WD wire protocol' support
  • 3
    Using a non-standard automation protocol

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is BrowserStack?

BrowserStack is a leading software testing platform for developers to comprehensively test their websites and mobile applications across 2,000+ real browsers and devices in a single cloud platform鈥攁nd at scale.

What is Cypress?

Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention BrowserStack and Cypress as a desired skillset
CBRE
Narva, Ida-Virumaa, Estonia
What companies use BrowserStack?
What companies use Cypress?
See which teams inside your own company are using BrowserStack or Cypress.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with BrowserStack?
What tools integrate with Cypress?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to BrowserStack and Cypress?
Browserling
We run the browsers on our servers. Fully interactive sessions, not static screenshots. No flash, no applets, nothing to install. Powered entirely by <canvas> and javascript.
LambdaTest
LambdaTest is a highly scalable testing platform on cloud. Mainly it provides Selenium Automation Grid with 2000+ browser-OS combinations, Cypress CLI test coverage to 40+ browser versions, and Mobile app testing infrastructure.
Ghost Inspector
It lets you create and manage UI tests that check specific functionality in your website or application. We execute these automated browser tests continuously from the cloud and alert you if anything breaks.
AWS Device Farm
Run tests across a large selection of physical devices in parallel from various manufacturers with varying hardware, OS versions and form factors.
Appium
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.
See all alternatives