CreateMock usage in e2e test

[christianvanr]

Hello,
I'm using the @nestjs/testing quite a lot, the createMock() is really helpful in all kind of scenarios.

The only thing I could not understand is when I'm using this in an e2e tests (or graphQl module/resolver test), the test will time out, in all other tests it works as expected.

Any ideas/suggestions, why this is not working (maybe related to the @Inject decorator?):

to reproduce it, you can scaffold a new application (nest new xx) , and modify the app.e2e-spec.ts (adding the mock and overrideProvider) , like this:

import * as request from 'supertest';

import { Test, TestingModule } from '@nestjs/testing';

import { AppModule } from './../src/app.module';
import { AppService } from './../src/app.service';
import { INestApplication } from '@nestjs/common';
import { createMock } from '@golevelup/ts-jest';


describe('AppController (e2e)', () => {
  let app: INestApplication;

  beforeEach(async () => {
    const moduleFixture: TestingModule = await Test.createTestingModule({
      imports: [AppModule],
    })
    .overrideProvider(AppService) 
    .useValue(createMock<AppService>()) // Mock the appservice
    .compile();

    app = moduleFixture.createNestApplication();
    await app.init();
  });

  it('/ (GET)', () => {
    return request(app.getHttpServer())
      .get('/')
      .expect(200)
      .expect('Hello World!');
  });
});

[christianvanr]

Unfortunately, I could not delete the previous post, but I found the problem/solution.
The supertest exception is a bit weird (when using the detecting with --detectOpenHandles), but basically for the methods which are used within the test, there should be an implementation (mock) (app.get<AppService>(AppService).getHello = jest.fn().mockReturnValue("Hello World!");