testing-nestjs VS graphql

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.

Let’s use the official documentation to follow the correct setup Documentation | NestJS - A progressive Node.js framework

Also use Express and Apollo, following Quick start.

This code demonstrates the centralized addition of a guard to a module, and by the way, NestJS v9 still doesn’t support this feature. In NestJS, adding a guard is supported only at the controller or method level, because the guard is not considered a provider.

To change your NestJS API into GraphQL, follow the GraphQL quickstart with NestJS and import the following code to your AppModule in src/app.module.ts.

Nest.js is an excellent alternative for GraphQL APIs building for Angular design and DDD lovers. Nest.js comes with:

[NestJS](https://docs.nestjs.com/graphql/quick-start)

I am interested in getting subscriptions working with federation. One solution I think is to run a separate non-federated end-point but I think NestJS has a bug where is merges the schemas. https://github.com/nestjs/graphql/issues/721 has been locked for over a year :(