Nest: Unit testing with Pipes and service

[kamilmysliwiec]

This is not a bug. Unit testing is useful for testing classes without any bounded dynamic metadata (in this case, without pipes). You shouldn't test pipe logic inside your controller .spec files. 🙂

[ghost]

@kamilmysliwiec righty looks like my mistake, thanks for the clarification

[ruscon]

@kamilmysliwiec, hi.
Can you show some examples(may be link?) for e2e test for controller with Pipe(), which makes external requests
I mean whether it is possible to somehow change(replace) the pipe through the DI ?

[paustria]

@kamilmysliwiec, hi.
Can you show some examples(may be link?) for e2e test for controller with Pipe(), which makes external requests
I mean whether it is possible to somehow change(replace) the pipe through the DI ?

This is how I mock pipe.

const mockSomeService = () => ({
  create: jest.fn(),
});

const mockSomePipe = jest.fn();

const module = await Test.createTestingModule({
      providers: [
        SomeResolver,
        {
          provide: SomeService,
          useFactory: mockSomeService,
        },
      ],
})
.overridePipe(SomePipe)
.useValue(mockSomePipe)
.compile();