Alternatives to Jasmine logo

Alternatives to Jasmine

Mocha, Jest, Karma, Cypress, and Enzyme are the most popular alternatives and competitors to Jasmine.
711
528
+ 1
168

What is Jasmine and what are its top alternatives?

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.
Jasmine is a tool in the Javascript Testing Framework category of a tech stack.
Jasmine is an open source tool with 14.6K GitHub stars and 2.2K GitHub forks. Here鈥檚 a link to Jasmine's open source repository on GitHub

Jasmine alternatives & related posts

related Mocha posts

Dschinkel Schinkel
Dschinkel Schinkel
Enzyme
Enzyme
React
React
JavaScript
JavaScript
Jest
Jest
Mocha
Mocha
#Testdrivendevelopment
#Bdd
#Tdd

I use both mocha and Jest because:

  • I don't care whether teams use Jest or Mocha. But jest is way too overhyped. Most devs are writing integration tests and think that it's so much better but frankly I don't write integration tests as the way to get both design feedback and confidence when I code. I adhere to the test pyramid, not ice cream cone or the dumb "trophy"

  • I TDD, so I only ever use the "API" of test frameworks. I don't do a lot of integration tests for TDD and all the bells and whistles Jest provides you from the command-line I just don't need. And I certainly do not care about or touch Jest Snapshots, I despise them

  • My tests are fast enough because I write isolated tests with TDD, so I don't run into performance issues. Example: I write my tests in a way that I can run 300 tests in literally 1 second with mocha. So the Jest ability to pinpoint and only run those tests which are affected by code changes. I want to run all of them every time when I TDD. It's a different mindset when you TDD

  • I also mainly code in IntelliJ or WebStorm because I feel the tools in that IDE far surpass VSCode and I also love running the test UI runner in it vs. lousy command-line

  • I feel both mocha and Jest read just fine in terms of code readability. Jest might have shorter assertion syntax but I don't really care. I just care that I can read the damn test and my tests are written well and my test descriptions, as well as the code itself including constants represent business language, not technical. I care most about BDD, clean code, 4 rules of simple design, and SOLID

  • I don't like using mock frameworks so no I don't use Jest's Mocking framework. I don't have to mock a lot in my tests due to the nature of how I strive to code...I keep my design simple and modular using principals such as clean code and 4 rules of simple design. If I must mock, I create very simple custom mocks with JS

  • On the contrary to the belief that integration tests and mount are the way to go (this belief drives me absolutely crazy, especially Dodd's promoting that), I TDD with shallow & enzyme. My tests are simple. My design is driven by my tests and my tests give me quick and useful feedback. I have a course I'm working on coming out soon on TDD with React to show you how to truly test the FE and why the ice cream cone and trophy suck (you're being scammed people). Watch for that here: https://twitter.com/DaveSchinkel/status/1062267649235791873

Don't forget to upvote this post!

Mocha Jest JavaScript React @jsdom Enzyme #tdd #bdd #testdrivendevelopment

See more
Jack Graves
Jack Graves
Head of Product Development at Automation Consultants | 3 upvotes 25.5K views
atAutomation ConsultantsAutomation Consultants
Mocha
Mocha
Apache JMeter
Apache JMeter
Jest
Jest
JUnit
JUnit

We use JUnit and Jest to perform the bulk of our automated test scenarios, with additional work with Apache JMeter for performance testing - for example, the Atlassian Data Center compliance testing is performed with JMeter. Jest provides testing for the React interfaces, which make up the backend of our App offerings. JUnit is used for Unit Testing our Server-based Apps. Mocha is another tool we use.

See more

related Jest posts

Robert Zuber
Robert Zuber
CTO at CircleCI | 15 upvotes 271.5K views
atCircleCICircleCI
Cypress
Cypress
Percy
Percy
Jest
Jest
Apollo
Apollo
GraphQL
GraphQL
Emotion
Emotion
TypeScript
TypeScript
Storybook
Storybook
React
React
Next.js
Next.js

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare | 7 upvotes 54.3K views
atStackShareStackShare
Percy
Percy
Happo.io
Happo.io
React Storybook
React Storybook
Enzyme
Enzyme
Jest
Jest

We use Jest because when we rebooted our "front end" stack earlier last year, we need to have a testing solution (we didn't have any front-end tests before that!). Jest is fast and convenient and it has plenty of community support behind it. It let's us run our unit tests with Enzyme and snapshot tests.

This is an area that we are constantly reviewing to see what can be improved, both in terms of developer needs, accuracy, test maintainability, and coverage.

I'm currently exploring using React Storybook to be the record of snapshot tests and using some online services, such as Happo.io and Percy in our CI pipeline.

See more
Karma logo

Karma

488
313
175
488
313
+ 1
175
Spectacular Test Runner for JavaScript
Karma logo
Karma
VS
Jasmine logo
Jasmine

related Karma posts

Visual Studio Code
Visual Studio Code
Jest
Jest
Angular CLI
Angular CLI
Karma
Karma
Jasmine
Jasmine

Switched from Jasmine with Karma that come setup by Angular CLI to use Jest instead, since Jasmine and Karma were very finicky in my setup and had to be reconfigured frequently to run tests properly.

Jest was also easier to integrate into my workflow with Visual Studio Code.

See more
Cypress logo

Cypress

279
147
22
279
147
+ 1
22
Better, faster, and more reliable testing for anything that runs in a browser.
Cypress logo
Cypress
VS
Jasmine logo
Jasmine

related Cypress posts

Robert Zuber
Robert Zuber
CTO at CircleCI | 15 upvotes 271.5K views
atCircleCICircleCI
Cypress
Cypress
Percy
Percy
Jest
Jest
Apollo
Apollo
GraphQL
GraphQL
Emotion
Emotion
TypeScript
TypeScript
Storybook
Storybook
React
React
Next.js
Next.js

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Jorge Quiros
Jorge Quiros
SR QA Automation Engineer at Indecomm | 8 upvotes 228.2K views
Cypress
Cypress
Selenium
Selenium
JavaScript
JavaScript
Jasmine
Jasmine
Protractor
Protractor
#Qaautomation
#Cypress
#Testing

This is a trending topic on Automation testing for E2E web applications.

I have used Protractor and Jasmine for automation testing frameworks in JavaScript by using the Selenium web driver manager.

Now, new guy in town Cypress does not use Selenium and runs directly in your app without any json wire protrocol, but it does not support parallel testing or mobile testing.

Have you experienced both? Should I stick with old and known ?

#testing cypress #selenium qaautomation #qa

See more
Enzyme logo

Enzyme

251
169
0
251
169
+ 1
0
JavaScript Testing utilities for React, by Airbnb
    Be the first to leave a pro
    Enzyme logo
    Enzyme
    VS
    Jasmine logo
    Jasmine

    related Enzyme posts

    Russel Werner
    Russel Werner
    Lead Engineer at StackShare | 7 upvotes 54.3K views
    atStackShareStackShare
    Percy
    Percy
    Happo.io
    Happo.io
    React Storybook
    React Storybook
    Enzyme
    Enzyme
    Jest
    Jest

    We use Jest because when we rebooted our "front end" stack earlier last year, we need to have a testing solution (we didn't have any front-end tests before that!). Jest is fast and convenient and it has plenty of community support behind it. It let's us run our unit tests with Enzyme and snapshot tests.

    This is an area that we are constantly reviewing to see what can be improved, both in terms of developer needs, accuracy, test maintainability, and coverage.

    I'm currently exploring using React Storybook to be the record of snapshot tests and using some online services, such as Happo.io and Percy in our CI pipeline.

    See more
    Dschinkel Schinkel
    Dschinkel Schinkel
    Enzyme
    Enzyme
    React
    React
    JavaScript
    JavaScript
    Jest
    Jest
    Mocha
    Mocha
    #Testdrivendevelopment
    #Bdd
    #Tdd

    I use both mocha and Jest because:

    • I don't care whether teams use Jest or Mocha. But jest is way too overhyped. Most devs are writing integration tests and think that it's so much better but frankly I don't write integration tests as the way to get both design feedback and confidence when I code. I adhere to the test pyramid, not ice cream cone or the dumb "trophy"

    • I TDD, so I only ever use the "API" of test frameworks. I don't do a lot of integration tests for TDD and all the bells and whistles Jest provides you from the command-line I just don't need. And I certainly do not care about or touch Jest Snapshots, I despise them

    • My tests are fast enough because I write isolated tests with TDD, so I don't run into performance issues. Example: I write my tests in a way that I can run 300 tests in literally 1 second with mocha. So the Jest ability to pinpoint and only run those tests which are affected by code changes. I want to run all of them every time when I TDD. It's a different mindset when you TDD

    • I also mainly code in IntelliJ or WebStorm because I feel the tools in that IDE far surpass VSCode and I also love running the test UI runner in it vs. lousy command-line

    • I feel both mocha and Jest read just fine in terms of code readability. Jest might have shorter assertion syntax but I don't really care. I just care that I can read the damn test and my tests are written well and my test descriptions, as well as the code itself including constants represent business language, not technical. I care most about BDD, clean code, 4 rules of simple design, and SOLID

    • I don't like using mock frameworks so no I don't use Jest's Mocking framework. I don't have to mock a lot in my tests due to the nature of how I strive to code...I keep my design simple and modular using principals such as clean code and 4 rules of simple design. If I must mock, I create very simple custom mocks with JS

    • On the contrary to the belief that integration tests and mount are the way to go (this belief drives me absolutely crazy, especially Dodd's promoting that), I TDD with shallow & enzyme. My tests are simple. My design is driven by my tests and my tests give me quick and useful feedback. I have a course I'm working on coming out soon on TDD with React to show you how to truly test the FE and why the ice cream cone and trophy suck (you're being scammed people). Watch for that here: https://twitter.com/DaveSchinkel/status/1062267649235791873

    Don't forget to upvote this post!

    Mocha Jest JavaScript React @jsdom Enzyme #tdd #bdd #testdrivendevelopment

    See more
    Protractor logo

    Protractor

    159
    109
    6
    159
    109
    + 1
    6
    End-to-end test framework for Angular and AngularJS applications
    Protractor logo
    Protractor
    VS
    Jasmine logo
    Jasmine

    related Protractor posts

    Jorge Quiros
    Jorge Quiros
    SR QA Automation Engineer at Indecomm | 8 upvotes 228.2K views
    Cypress
    Cypress
    Selenium
    Selenium
    JavaScript
    JavaScript
    Jasmine
    Jasmine
    Protractor
    Protractor
    #Qaautomation
    #Cypress
    #Testing

    This is a trending topic on Automation testing for E2E web applications.

    I have used Protractor and Jasmine for automation testing frameworks in JavaScript by using the Selenium web driver manager.

    Now, new guy in town Cypress does not use Selenium and runs directly in your app without any json wire protrocol, but it does not support parallel testing or mobile testing.

    Have you experienced both? Should I stick with old and known ?

    #testing cypress #selenium qaautomation #qa

    See more
    AVA logo

    AVA

    86
    89
    28
    86
    89
    + 1
    28
    A refined, futuristic test runner
    AVA logo
    AVA
    VS
    Jasmine logo
    Jasmine
    Chai logo

    Chai

    74
    22
    0
    74
    22
    + 1
    0
    A BDD / TDD assertion library
      Be the first to leave a pro
      Chai logo
      Chai
      VS
      Jasmine logo
      Jasmine

      related Chai posts

      Visual Studio Code
      Visual Studio Code
      Chai
      Chai
      Mocha
      Mocha
      Sequelize
      Sequelize
      Logstash
      Logstash
      Kibana
      Kibana
      Elasticsearch
      Elasticsearch
      ExpressJS
      ExpressJS
      Node.js
      Node.js
      LoopBack
      LoopBack
      React
      React

      React LoopBack Node.js ExpressJS Elasticsearch Kibana Logstash Sequelize Mocha Chai Visual Studio Code are the combo of technologies being used by me to build BestPrice Extension with all its micro-services & Web-based fragments

      See more
      SinonJS logo

      SinonJS

      53
      13
      0
      53
      13
      + 1
      0
      Standalone test spies, stubs and mocks for JavaScript
        Be the first to leave a pro
        SinonJS logo
        SinonJS
        VS
        Jasmine logo
        Jasmine
        QUnit logo

        QUnit

        47
        37
        13
        47
        37
        + 1
        13
        A JavaScript Unit Testing framework
        QUnit logo
        QUnit
        VS
        Jasmine logo
        Jasmine
        SuperTest logo

        SuperTest

        19
        5
        0
        19
        5
        + 1
        0
        A library for testing node.js HTTP servers
          Be the first to leave a pro
          SuperTest logo
          SuperTest
          VS
          Jasmine logo
          Jasmine
          CodeceptJS logo

          CodeceptJS

          13
          10
          20
          13
          10
          + 1
          20
          Modern End 2 End Testing Framework for NodeJS
          CodeceptJS logo
          CodeceptJS
          VS
          Jasmine logo
          Jasmine
          Majestic GUI logo

          Majestic GUI

          1
          6
          0
          1
          6
          + 1
          0
          Zero config GUI for Jest
            Be the first to leave a pro
            Majestic GUI logo
            Majestic GUI
            VS
            Jasmine logo
            Jasmine
            Vorlon.JS logo

            Vorlon.JS

            1
            2
            0
            1
            2
            + 1
            0
            An open source, extensible, platform-agnostic tool for remotely debugging and testing your JavaScript
              Be the first to leave a pro
              Vorlon.JS logo
              Vorlon.JS
              VS
              Jasmine logo
              Jasmine