javascript-testing-best-practices VS testcontainers-node

😎 You want to take your JS testing skills to the next level, here is a nice repo -> javascript-testing-best-practices

Surprised nobody referred this

Yoni Golberg's JavaScript Testing best practices guide is always a good resource to consult, for both beginners and experienced developers: https://github.com/goldbergyoni/javascript-testing-best-practices

I really like how testing is done in Rails. Why did you choose the snapshots approach? I never have seen it for this purpose, they say it's bad practice even for the frontend (check testing practices for node btw), so, why?

JavaScript Testing Best Practices, by Yoni Goldberg is a GitHub repository. It gives good practices about testing.

I recently found one of my own forgotten PRs from about two years ago where I added a new module to the testcontainers-node library. (https://github.com/testcontainers/testcontainers-node/pull/646) I wanted to tell the story of that contribution, but I didn't want to spend hours writing it from scratch.

Fortunately, there is an awesome project for that named TestContainers.

Testcontainers solves this problem elegantly by providing a way to run lightweight, throwaway instances of databases, message brokers, web servers, and other services directly within your test suite. Instead of complex setup scripts or shared test environments, you can spin up real services in Docker containers that exist only for the duration of your tests. The core value proposition is compelling: write tests that run against the actual technologies your application uses in production, while maintaining the isolation and repeatability that good tests require. When your tests complete, the containers are automatically cleaned up, leaving no trace behind.

This article covers how to use Docker for integration testing in an ASP.NET Core Web API project. We'll use the Testcontainers library to spin up SQL Server containers for our integration tests.

A great alternative is testcontainers + testcontainers Cloud. Testcontainers is a library available in many languages that allows you to start and stop Docker containers during your tests, making it possible to get good isolation between tests. Testcontainers Cloud is a service that allows you to run said containers on a remote infrastructure, as opposed to running them on your own infrastructure, which, if you want to use Kubernetes runners for Gitlab, implies using Docker in Docker, which is not great from the security standpoint. Locally, you would still use a local docker container, but in the CI, tescontainers will send requests to testcontainers cloud, to start and stop containers. Enough unpaid endorsement, let's get to the code.

There’s also https://testcontainers.com/ not sure about the speed difference but testcontainers has never felt slow to me when using it from node js unittests.

Even though we’re going to be using the Java TestContainers project here, TestContainers is available for lots of languages and platforms. You can check it out on their website.

Start Docker Compose with both Ollama and PGVector using Testcontainers