What is AVA and what are its top alternatives?
Top Alternatives to AVA
- Jest
Jest provides you with multiple layers on top of Jasmine.
- EVA
Equipping you with hundreds of symbols and dozens or styles configurations, it makes sure the design stays consistent across all of your applications and platforms. ...
- 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. ...
- 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. ...
- 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. ...
- 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. ...
- 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. ...
- 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. ...
AVA alternatives & related posts
- Open source36
- Mock by default makes testing much simpler32
- Testing React Native Apps23
- Parallel test running20
- Fast16
- Bundled with JSDOM to enable DOM testing13
- Mock by default screws up your classes, breaking tests8
- Out of the box code coverage7
- Promise support7
- One stop shop for unit testing6
- Great documentation3
- Assert Library Included2
- Built in watch option with interactive filtering menu1
- Preset support1
- Can be used for BDD0
- Karma0
- Documentation4
- Ambiguous configuration4
- Difficult3
- Many bugs still not fixed months/years after reporting2
- Multiple error messages for same error2
- Difficult to run single test/describe/file2
- Ambiguous2
- Bugged2
- BeforeAll timing out makes all passing tests fail1
- Slow1
- Reporter is too general1
- Unstable1
- Bad docs1
- Still does't support .mjs files natively1
- Can't fail beforeAll to abort tests1
- Interaction with watch mode on terminal0
related Jest posts
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.
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.
related EVA posts
Mocha
- Open source137
- Simple102
- Promise support81
- Flexible48
- Easy to add support for Generators29
- For browser and server testing12
- Curstom assertion libraries7
- Works with Karma5
- No other better tools3
- Simple setup1
- Works with saucelabs1
- Lots of tutorials and help online1
- Default reporter is nice, clean, and itemized1
- Works with BrowserStack1
- Simple integration testing1
- Cannot test a promisified functions without assertion3
- No assertion count in results2
- Not as many reporter options as Jest1
related Mocha 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
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.
related Chai posts
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.
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
- Can also be used for tdd64
- Open source49
- Originally from RSpec18
- Great community15
- No dependencies, not even DOM14
- Easy to setup10
- Simple8
- Created by Pivotal-Labs3
- Works with KarmaJs2
- Jasmine is faster than selenium in angular application1
- SpyOn to fake calls1
- Async and promises are easy calls with "done"1
- Unfriendly error logs2
related Jasmine posts
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.
Protractor or Cypress for ionic-angular?
We have a huge ionic-angular app with almost 100 pages and 10+ injectables. There are no tests written yet. Before we start, we need some suggestions about the framework. Would you suggest Cypress or Angular's Protractor with Jasmine / Karma for a heavy ionic app with Angular?
- Open source1
- More concepts than Jest1
- Less questions and answers on StackOverflow than Jest1
related SinonJS posts
Cypress
- Open source29
- Great documentation22
- Simple usage20
- Fast18
- Cross Browser testing10
- Easy us with CI9
- Npm install cypress only5
- Good for beginner automation engineers1
- Cypress is weak at cross-browser testing21
- Switch tabs : Cypress can'nt support14
- No iFrame support12
- No page object support9
- No multiple domain support9
- No file upload support8
- No support for multiple tab control8
- No xPath support8
- No support for Safari7
- Cypress doesn't support native app7
- Re-run failed tests retries not supported yet7
- No support for multiple browser control7
- $20/user/thread for reports5
- Adobe4
- Using a non-standard automation protocol4
- Not freeware4
- No 'WD wire protocol' support3
related Cypress posts
When you think about test automation, it’s crucial to make it everyone’s 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.
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.
- Easy setup9
- Quick tests implementation8
- Flexible6
- Open source5
- Promise support5
- Limited4
related Protractor posts
Currently, we are using Protractor in our project. Since Protractor isn't updated anymore, we are looking for a new tool. The strongest suggestions are WebdriverIO or Puppeteer. Please help me figure out what tool would make the transition fastest and easiest. Please note that Protractor uses its own locator system, and we want the switch to be as simple as possible. Thank you!
Protractor or Cypress for ionic-angular?
We have a huge ionic-angular app with almost 100 pages and 10+ injectables. There are no tests written yet. Before we start, we need some suggestions about the framework. Would you suggest Cypress or Angular's Protractor with Jasmine / Karma for a heavy ionic app with Angular?