The death of mocks by Testcontainers

1. nest-js-integration-test-with-testcontainers

   1 1 0 6.3 TypeScript

   

   Kindly note I would mostly skip the setup required to run the NestJs application, here's a link to the Github Repository.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. testcontainers-node

   2 50 2,053 8.4 TypeScript

   Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.

   

   Writing tests can often feel like a daunting task, especially when you find yourself juggling mocks for internal and external services. Flaky tests, unrealistic mocks, and the constant fear of “what if this breaks in production?” can make the process incredibly stressful. I recently had to write integration tests for a service built with NestJs and having to mock the database layer (repository) didn't sit right with me as it felt like I was testing a facade rather than the real thing. Now, don’t get me wrong—mocks are great and have their place in testing. But in this scenario, I wanted to ensure my code worked seamlessly in a production-like environment. So, I did what any developer would do: I reached out to my manager for advice. His suggestion? Testcontainers. It was a game-changer. With Testcontainers, I was able to spin up lightweight, disposable containers for services like PostgreSQL, Redis, and more—giving me a reliable, production-like testing environment right from my local machine. No more “living a lie” with overly simplistic mocks.

4. Nest

   3 365 69,881 9.9 TypeScript

   A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀

   

   Writing tests can often feel like a daunting task, especially when you find yourself juggling mocks for internal and external services. Flaky tests, unrealistic mocks, and the constant fear of “what if this breaks in production?” can make the process incredibly stressful. I recently had to write integration tests for a service built with NestJs and having to mock the database layer (repository) didn't sit right with me as it felt like I was testing a facade rather than the real thing. Now, don’t get me wrong—mocks are great and have their place in testing. But in this scenario, I wanted to ensure my code worked seamlessly in a production-like environment. So, I did what any developer would do: I reached out to my manager for advice. His suggestion? Testcontainers. It was a game-changer. With Testcontainers, I was able to spin up lightweight, disposable containers for services like PostgreSQL, Redis, and more—giving me a reliable, production-like testing environment right from my local machine. No more “living a lie” with overly simplistic mocks.

Suggest a related project