Alternatives to Mocha logo

Alternatives to Mocha

Jasmine, Jest, Chai, Cypress, and Enzyme are the most popular alternatives and competitors to Mocha.
3.4K
2.4K
+ 1
415

What is Mocha and what are its top alternatives?

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

Top Alternatives to Mocha

  • Jasmine

    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. ...

  • Jest

    Jest

    Jest provides you with multiple layers on top of Jasmine.

  • Chai

    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. ...

  • Cypress

    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. ...

  • Enzyme

    Enzyme

    Enzyme is a JavaScript Testing utility for React that makes it easier to assert, manipulate, and traverse your React Components' output. ...

  • SinonJS

    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. ...

  • SuperTest

    SuperTest

    It is a super-agent driven library for testing node.js HTTP servers using a fluent API. It provides a high-level abstraction for testing HTTP, while still allowing you to drop down to the lower-level API provided by superagent. ...

  • Protractor

    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. ...

Mocha alternatives & related posts

related Jasmine posts

Joshua Dean K眉pper
CEO at Scrayos UG (haftungsbeschr盲nkt) | 6 upvotes 路 30.3K views

For our internal team and collaboration panel we use Nuxt.js (with TypeScript that is transpiled into ES6), Webpack and npm. We enjoy the opinionated nature of Nuxt.js over vanilla Vue.js, as we would end up using all of the components Nuxt.js incorporates anyways and we can adhere to the conventions setup by the Nuxt.js project, which allows us to get better support in case we run into any dead ends. Webpack allows us to create reproducable builds and also debug our application with hot reloads, which greately increased the pace at which we are able to perform and test changes. We also incorporated a lot of testing (ESLint, Chai, Jasmine, Nightwatchjs) into our pipelines and can trigger those jobs through GitLab CI. All packages are fetched through npm, so that we can keep our git repositories slim and are notified of new updates aswell as reported security flaws.

See more

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

related Jest posts

Robert Zuber

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
Shared insights
on
Cypress
Jest

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
Chai logo

Chai

663
113
0
A BDD / TDD assertion library
663
113
+ 1
0
PROS OF CHAI
    No pros available
    CONS OF CHAI
      No cons available

      related Chai posts

      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 6 upvotes 路 30.3K views

      For our internal team and collaboration panel we use Nuxt.js (with TypeScript that is transpiled into ES6), Webpack and npm. We enjoy the opinionated nature of Nuxt.js over vanilla Vue.js, as we would end up using all of the components Nuxt.js incorporates anyways and we can adhere to the conventions setup by the Nuxt.js project, which allows us to get better support in case we run into any dead ends. Webpack allows us to create reproducable builds and also debug our application with hot reloads, which greately increased the pace at which we are able to perform and test changes. We also incorporated a lot of testing (ESLint, Chai, Jasmine, Nightwatchjs) into our pipelines and can trigger those jobs through GitLab CI. All packages are fetched through npm, so that we can keep our git repositories slim and are notified of new updates aswell as reported security flaws.

      See more

      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

      related Cypress posts

      Kamil Kowalski
      Engineering Manager at Fresha | 27 upvotes 路 710.5K views

      When you think about test automation, it鈥檚 crucial to make it everyone鈥檚 responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

      See more
      Robert Zuber

      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
      Enzyme logo

      Enzyme

      411
      295
      0
      JavaScript Testing utilities for React, by Airbnb
      411
      295
      + 1
      0
      PROS OF ENZYME
        No pros available
        CONS OF ENZYME
          No cons available

          related Enzyme posts

          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
          Russel Werner
          Lead Engineer at StackShare | 6 upvotes 路 124.4K views

          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
          SinonJS logo

          SinonJS

          408
          26
          1
          Standalone test spies, stubs and mocks for JavaScript
          408
          26
          + 1
          1

          related SinonJS posts

          SuperTest logo

          SuperTest

          373
          29
          0
          A library for testing node.js HTTP servers
          373
          29
          + 1
          0
          PROS OF SUPERTEST
            No pros available
            CONS OF SUPERTEST
              No cons available

              related SuperTest posts

              Protractor logo

              Protractor

              298
              327
              21
              End-to-end test framework for Angular and AngularJS applications
              298
              327
              + 1
              21

              related Protractor posts