APP_INITIALIZER contract not honoured with TestBed

[victornoel]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

When importing a Module providing a promise-based APP_INITIALIZER into a TestBed, the tests are executed before the promise is fully resolved.

There was an issue for this very problem (#16204) but the reporter closed because he found a workaround.

Expected behavior

The promise of an APP_INITIALIZER should be fully resolved, exactly as when running the application that uses this module normally.

Minimal reproduction of the problem with instructions

Hadn't had the time, but I expect that it should be simple to know if is already implemented or not to behave like expected. If yes, I will produce a repro.

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

Same contract with tests or real app.

Environment

Angular version: 6.0.7

[victornoel]

For the record, a solution until this is fixed, is to add the following beforeEach in your jasmine tests (after compileComponents() and before createComponent() for example):

  beforeEach(async () => {
    // until https://github.com/angular/angular/issues/24218 is fixed
    await TestBed.get(ApplicationInitStatus).donePromise;
  });

[victornoel]

@vicb are you expecting a repro before this is taken care of? Or is the angular team going to take a look directly at the code.

This doesn't seem to be a bug, regression or a corner case but a very clearly missing feature…

[dydFreeman]

Any update on this?

P.s: @victornoel your workaround saved my day ; )

[victornoel]

@vicb ping? :)

[victornoel]

@vicb ping

[rgant]

This causes my app confusion regularly in testing. The errors are always so difficult to hunt down because they are cryptic, but I need APP_INITIALIZER to complete before the tests run.