rescript-test VS mocha

Besides bindings for JavaScript libraries, there is rescript-test - a lightweight test framework written in ReScript for ReScript. I have heard that some people like it, but for me, it lacks coverage output and Wallaby support.

As soon as you need to change the name or something, delete a field, or change a field… you’ve broken the API. This means you first need to change your Lambda(s) that use this new data, and ensure your unit tests (using ReTest) pass, and your integration tests (using Mocha & JavaScript) which invoke your Lambdas directly on a QA server still work.

To do that, we’re using rescript-test, which feels natural to those used to Jest, Mocha, etc. The only main difference is using testAsync vs test for async code, and having to define your own assertions vs. “Jest/Chai has ALL THE THINGS”.

MochaJS is a feature-rich JavaScript test framework running on Node.js, making it a popular choice for both backend and frontend testing. It's known for its flexibility and straightforward syntax, allowing for asynchronous testing and the use of any assertion library.

We use Jest Framework for testing. Jest is not a dogma, and, of course, in its place can be any other test runner, such as Mocha or Ava. Let's focus on tests. I'll provide a short example because I don’t want to waste your time. You can find the full version here. It's crucial to read the comments in the code below. Let's go!

JavaScript Popular tools for testing: Mocha, Jasmine, Unit JS, Jest

To execute your tests, you can create test scripts using popular testing frameworks like Mocha, Jasmine, or Jest. These frameworks provide a structured way to organize and run your tests, report results, and handle assertions.

⚗️ Mocha and Chai for testing

Testing frameworks like Jest, Mocha, and Jasmine are crucial for software development, ensuring code reliability and correctness. They offer features like test suites, test cases, assertions, and asynchronous testing support.

JavaScript / JEST / Mocha