Alternatives to AVA logo

Alternatives to AVA

Jest, Mocha, Jasmine, Cypress, and Enzyme are the most popular alternatives and competitors to AVA.
89
127
+ 1
32

What is AVA and what are its top alternatives?

Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file.
AVA is a tool in the Javascript Testing Framework category of a tech stack.
AVA is an open source tool with 17.8K GitHub stars and 1.2K GitHub forks. Here鈥檚 a link to AVA's open source repository on GitHub

Top Alternatives of AVA

AVA alternatives & related posts

related Jest posts

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

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
Cypress
Cypress
Jest
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

related Mocha posts

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

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 63.6K views
atAutomation ConsultantsAutomation Consultants
JUnit
JUnit
Jest
Jest
Apache JMeter
Apache JMeter
Mocha
Mocha

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 Jasmine posts

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

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

488
464
52
488
464
+ 1
52
Better, faster, and more reliable testing for anything that runs in a browser.
Cypress logo
Cypress
VS
AVA logo
AVA

related Cypress posts

Kamil Kowalski
Kamil Kowalski
Engineering Manager at Fresha | 26 upvotes 210.6K views
atFresha EngineeringFresha Engineering
Selenium
Selenium
Java
Java
Ruby
Ruby
Elixir
Elixir
JavaScript
JavaScript
Cypress
Cypress

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
Robert Zuber
CTO at CircleCI | 17 upvotes 482.7K views
atCircleCICircleCI
Next.js
Next.js
React
React
Storybook
Storybook
TypeScript
TypeScript
Emotion
Emotion
GraphQL
GraphQL
Apollo
Apollo
Jest
Jest
Percy
Percy
Cypress
Cypress

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

338
218
0
338
218
+ 1
0
JavaScript Testing utilities for React, by Airbnb
    Be the first to leave a pro
    Enzyme logo
    Enzyme
    VS
    AVA logo
    AVA

    related Enzyme posts

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

    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
    Russel Werner
    Lead Engineer at StackShare | 6 upvotes 99.2K views
    atStackShareStackShare
    Jest
    Jest
    Enzyme
    Enzyme
    React Storybook
    React Storybook
    Happo.io
    Happo.io
    Percy
    Percy

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

    Protractor

    207
    199
    13
    207
    199
    + 1
    13
    End-to-end test framework for Angular and AngularJS applications
    Protractor logo
    Protractor
    VS
    AVA logo
    AVA
    Chai logo

    Chai

    147
    70
    0
    147
    70
    + 1
    0
    A BDD / TDD assertion library
      Be the first to leave a pro
      Chai logo
      Chai
      VS
      AVA logo
      AVA

      related Chai posts

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

      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

      71
      20
      1
      71
      20
      + 1
      1
      Standalone test spies, stubs and mocks for JavaScript
      SinonJS logo
      SinonJS
      VS
      AVA logo
      AVA