InversifyJS VS testing-nestjs

Take a class for which we are tasked to write a unit test. This class may have a dozen methods and a dozen more attributes. In my environment we were already using inversify to dependency inject into this class, and using container snapshot and restore as setup and teardown operators, in our jest test file. But it began getting out of control even after refactoring into test cases and test runners.

Inversify (https://inversify.io/) for IoC.

Alguns frameworks trabalham desta forma por padrão, como é o caso do Angular, quando este não é o padrão do framework que utilizamos podemos usar alguma biblioteca, como a Inversify ou tsyringe da Microsoft.

Using decorators required setting an --experimentalDecorators experimental compiler flag. Several popular TypeScript libraries, such as type-graphql and inversify, rely on this implementation.

inversify

It blows 🤯 my mind to think that my #opensource project InversifyJS has reached over 100 MILLION DOWNLOADS on npm. InversifyJS is a lightweight (<50KB) but powerful Inversion Of Control (IoC) container for #JavaScript applications powered by #TypeScript. It is used to implement Dependency Injection (DI) in thousands of applications, including high-profile products like Microsoft Sway and over forty thousand open source repositories on #GitHub and over two thousand open source packages on #npm.

we use https://inversify.io/ in production, it works great.

To echo the other's here, Nx has been an amazing dev experience for me! I use it for ogma, for nest-commander, testing-nestjs, and for nest-samples and @nest-lab/, all using pnpm as a package manager.

The prisma sample app in the testing-nestjs repository does a great job on showing how to do testing a NestJS app with Prisma.

Example https://github.com/jmcdo29/testing-nestjs/blob/8519ae7043d1dde5ae12a5d8f8ab02ea3c3c2fcf/apps/complex-sample/src/cat/cat.interceptor.spec.ts

Question: for your e2e tests will you be using something like supertestto send the gql request? And if so, could I suggest you look at pactum which (in my opinion) has a stronger API and better gql support. I've got an example here if you need it

Test files usually shouldn't be too large. You should just need a simple mock for each injected dependency for the service. You can see a lot of examples I have here. If you could show your test file it may help us figure out why it might be really large.

Then there's also a @nestjs/testing package that can be used for overriding these injections during tests to make for super easy unit testing (in my opinion) and a large repo of examples here.