2023-02-08
4365
#jest#react
Murat Çatal
11926
Feb 8, 2023 ⋅ 15 min read

Comparing React testing libraries

Murat Çatal I have over nine years of hands-on development experience as a fullstack developer, including technical lead positions. Currently overseeing development of enterprise applications, leading the frontend team.

Recent posts:

Parsing PDFs in Node.js

Parsing PDFs in Node.js

This guide covers the top npm packages for parsing PDFs in Node.js, including pdf-parse, pdf2json, and pdfreader.

Chibuike Nwachukwu
Mar 4, 2024 ⋅ 7 min read
Implementing In App Updates For React Native Apps

Implementing in-app updates for React Native apps

Implementing OTA in-app updates in React Native apps can streamline the update process, preventing delays that hinder overall productivity.

Nelson Michael
Mar 1, 2024 ⋅ 7 min read
Exploring Stylex And The New Generation Of Styling Libraries

Exploring StyleX and the new generation of styling libraries

StyleX is a build-time, type-safe CSS-in-JS library recently open sourced by Meta. Explore StyleX and the evolution of styling libraries.

Ibadehin Mojeed
Feb 29, 2024 ⋅ 9 min read
Building High Performance Ecommerce Sites With Astro

Building high-performance ecommerce sites with Astro

Learn to set up a completely custom Astro ecommerce implementation that’s also highly performant and type-safe in this straightforward guide.

Onuorah Bonaventure
Feb 28, 2024 ⋅ 64 min read
View all posts

6 Replies to "Comparing React testing libraries"

  1. How come Cypress gets four stars for browser support when it only works in Chrome? The entire post is flawed but this has really triggered me.

  2. Hi Milos,

    Thanks for your comment. But there is not any technical problem in document. Cypress supports Canary, Chrome, Chromium and Electron, so got 4 star while puppeteer only supports chromium and gets one star. In addition to that, cypress has roadmap (https://github.com/cypress-io/cypress/issues/3207) for supporting firefox and ie11, also that feature will make it even stronger in near future so it deserves 4 star for me.

    Reference document https://docs.cypress.io/guides/guides/launching-browsers.html#Browsers

    Also, that document is created by prior experiences plus current documents of libraries. You may not be with same idea about authors’ personal comments (about that given stars…), but it is not right you to call whole work as useless and flawed.

  3. For end to end, @DXTestCafe should have been considered. Apart from awesome ES6 support, we can test on different browsers while Cypress and Puppeteer are Chrome browser constrained as of now.

  4. I am not sure it is! could you elaborate more on why you think the post is flawed?

    Also Cypress supports a wide range of browsers including Edge, Firefox and Electron (including unstable channels like dev and canary to test against future releases), the only reason that triggered you is actually not true.

    There is also a Safari Support request that is currently being evaluated: https://github.com/cypress-io/cypress/issues/6422.

Leave a Reply