Add init() to the application context interface

[ghost]

Hi guys,

for purpose of unit testing & integration testing, is there any way of having lifecycle events executed with TestingModule without calling createApplication? It would be great if you wouldn't have to start express server for each unit test and would have Init and Destroy lifecycle events properly executed after compilation of a testing module, or after calling some kind of init().

[ ] Regression 
[ ] Bug report
[x ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Lifecycle events not being executed within TestModule without creating express application.

Expected behavior

Lifecycle events get executed within TestModule after compilation or after calling some kind of init() or createApplicationContext().

Minimal reproduction of the problem with instructions

  beforeEach(async () => {
    const module = await Test.createTestingModule({
        imports: [CommonModule],
        providers: [CatsService],
      }).compile();

    catsService = module.get<CatsService>(CatsService);
  });

In this example, if CommonModule has lots of services which need proper initialisation and cleanup in OnModuleInit & OnModuleDestroy handlers, we are not able to init() the module without calling createApplication which will start express server.

What is the motivation / use case for changing the behavior?

Environment

Nest version: 5.7.1

 
For Tooling issues:
- Node version: 10.14.0
- Platform:  Mac

Others:

Many thanks

[kamilmysliwiec]

close() should be available. We need to add init() though

[kamilmysliwiec]

Published as 6.3.0

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.