jest-mock-extended VS testcontainers-node

Create a mock of the Repository that you're testing, it's the simplest one and the more cumbersome one, you can use a library like jest-create-mock-instance or jest-mock-extended or ts-auto-mock to create a mock from typings, but you're responsible to implement how it supposes to work.

You can use something like jest-mock-extended or @golevelup/ts-jest to mock it, and whether your interceptor has dependencies or not, can be more complex or simpler how you instance it.

how does this compare to jest-mock-extended?

To be able to test for multiple databases, I recommend you using Testcontainers. That's my configuration to start the container:

I don't get it either. Why not use something like https://testcontainers.com/?

Testing with added infrastructure can be quite tricky. testcontainers aims to solve this by providing an open-source framework for providing local, lightweight containers for your application that can be immediately thrown away after use. It also has a Rust SDK!

This is a good start. But DynamoDB Local is a great fit for Testcontainers which "is an open source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container."

Devservices supports the automatic provisioning of unconfigured third party services in development and test mode. They can be provided by extension leveraging (usually) TestContainer library.

I hadn’t heard of Test Containers[1], but it looks really useful - thanks for the rec.

[1] https://testcontainers.com/