Processor/Job doesn't run when testing Queues about bull

[kamilmysliwiec]

We bind processors on the onModuleInit hook. To trigger it, you have to call await app.init() after compile()

[kamilmysliwiec]

You can follow this example: https://github.com/nestjs/bull/blob/master/e2e/module.e2e-spec.ts which seems to solve the same problem as you described

[VictorGaiva]

Yep that's it. Thanks.

I believe it would be convenient to add this piece of information to the @nestjs Queues documentation and this referenced Example. I'll work on a PR for each.

[VictorGaiva]

The example uses jest.fn() to mock the Consumer, seen here.

There repo I linked has two test scripts:

• app.module.spec.ts which tests if the message was added to the Queue and processed by the mockFn, as done in the example. It uses a app.controller.ts to adds a job, which is done as a side effect.
• app.processor.spec.ts which retrieves the Queue itself, manually adds the job and creates a Promise to expect the job to return the same data I sent.

The second is the one attempts to use the Process defined in app.processor.ts. The example you linked doesn't cover this case. It uses mock functions in all tests.

[francesca-giammichele-mahana]

https://github.com/nestjs/bull/blob/master/e2e/module.e2e-spec.ts

forgive me, the provided link is not working anymore :(

[micalevisk]

@radacat2121 https://github.com/nestjs/bull/blob/master/packages/bull/e2e/module.e2e-spec.ts