Jasmine聽vs聽Jest聽vs聽Protractor

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

Jasmine

1.5K
1.3K
+ 1
183
Jest

4.1K
2.5K
+ 1
167
Protractor

623
440
+ 1
26
Advice on Jasmine, Jest, and Protractor
Yildiz Dila
testmanager/automation tester at medicalservice | 5 upvotes 路 123.7K views
Needs advice
on
Protractor
and
Cypress

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 路 45.1K 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 路 74K 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 Jasmine, Jest, and Protractor
Shared insights
on
Jest
Cypress

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

Postman will be used to do integration testing with the backend API we create. It offers a clean interface to create many requests, and you can even organize these requests into collections. It helps to test the backend API first to make sure it's working before using it in the front-end. Jest can also be used for testing and is already embedded into React. Not only does it offer unit testing support in javascript, it can also do snapshot testing for the front-end to make sure components are rendering correctly. Enzyme is complementary to Jest and offers more functions such as shallow rendering. UnitTest will be used for Python testing as it is simple, has a lot of functionality and already built in with python. Sentry will be used for keeping track of errors as it is also easily integratable with Heroku because they offer it as an add-on. LogDNA will be used for tracking logs which are not errors and is also a Heroku add-on. Its good to have a separate service to record logs, monitor, track and even fix errors in real-time so our application can run more smoothly.

See more

We use Mocha for our FDA verification testing. It's integrated into Meteor, our upstream web application framework. We like how battle tested it is, its' syntax, its' options of reporters, and countless other features. Most everybody can agree on mocha, and that gets us half-way through our FDA verification and validation (V&V) testing strategy.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Jasmine
Pros of Jest
Pros of Protractor
  • 62
    Can also be used for tdd
  • 49
    Open source
  • 17
    Originally from RSpec
  • 15
    Great community
  • 14
    No dependencies, not even DOM
  • 10
    Easy to setup
  • 8
    Simple
  • 3
    Created by Pivotal-Labs
  • 2
    Works with KarmaJs
  • 1
    Async and promises are easy calls with "done"
  • 1
    Jasmine is faster than selenium in angular application
  • 1
    SpyOn to fake calls
  • 35
    Open source
  • 31
    Mock by default makes testing much simpler
  • 22
    Testing React Native Apps
  • 19
    Parallel test running
  • 15
    Fast
  • 13
    Bundled with JSDOM to enable DOM testing
  • 7
    Out of the box code coverage
  • 7
    Mock by default screws up your classes, breaking tests
  • 6
    One stop shop for unit testing
  • 6
    Promise support
  • 3
    Great documentation
  • 1
    Built in watch option with interactive filtering menu
  • 1
    Preset support
  • 1
    Assert Library Included
  • 0
    Can be used for BDD
  • 8
    Easy setup
  • 7
    Quick tests implementation
  • 4
    Open source
  • 4
    Promise support
  • 3
    Flexible

Sign up to add or upvote prosMake informed product decisions

Cons of Jasmine
Cons of Jest
Cons of Protractor
  • 2
    Unfriendly error logs
  • 3
    Ambiguous configuration
  • 3
    Documentation
  • 2
    Difficult
  • 2
    Multiple error messages for same error
  • 2
    Ambiguous
  • 2
    Many bugs still not fixed months/years after reporting
  • 2
    Difficult to run single test/describe/file
  • 1
    Can't fail beforeAll to abort tests
  • 1
    Bugged
  • 1
    Reporter is too general
  • 1
    Meh
  • 1
    BeforeAll timing out makes all passing tests fail
  • 1
    Unstable
  • 1
    Bad docs
  • 1
    Still does't support .mjs files natively
  • 0
    Interaction with watch mode on terminal
  • 3
    Limited

Sign up to add or upvote consMake informed product decisions

What is Jasmine?

Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js projects, or anywhere that JavaScript can run.

What is Jest?

Jest provides you with multiple layers on top of Jasmine.

What is Protractor?

Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.

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

What companies use Jasmine?
What companies use Jest?
What companies use Protractor?

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

What tools integrate with Jasmine?
What tools integrate with Jest?
What tools integrate with Protractor?

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

Blog Posts

What are some alternatives to Jasmine, Jest, and Protractor?
Mocha
Mocha is a feature-rich JavaScript test framework running on node.js and the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases.
Karma
Karma is not a testing framework, nor an assertion library. Karma just launches a HTTP server, and generates the test runner HTML file you probably already know from your favourite testing framework. So for testing purposes you can use pretty much anything you like.
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.
Chai
It is a BDD / TDD assertion library for node and the browser that can be delightfully paired with any javascript testing framework. It has several interfaces that allow the developer to choose the most comfortable. The chain-capable BDD styles provide an expressive language & readable style, while the TDD assert style provides a more classical feel.
SinonJS
It is a really helpful library when you want to unit test your code. It supports spies, stubs, and mocks. The library has cross browser support and also can run on the server using Node.js.
See all alternatives