Bug: Ng19=next - Forgot to flush TestBed? MockRender cannot be used without a reset

[DDtMM]

Description of the bug

After upgrading to Angular 19.0.0-next.11 from Angular 18.x my tests my tests that use MockRender started getting the error: "Forgot to flush TestBed? MockRender cannot be used without a reset..." These tests all worked properly before. I also tried taking the advice and calling MockRender like this fixture = MockRender('', {}, { reset: true });, but it did not help.

An example of the bug

You can see an example of the Angular 18 versions here: https://github.com/DDtMM/angular-signal-generators/blob/main/projects/signal-generators/src/lib/signals/tween-signal.spec.ts. The stack trace pointed to the MockRender() calls in the beforeEach. I'm assuming Angular changed something that affects ngMocks since I'm using it in a very minimal fashion for my project.

 beforeEach(() => {
    fixture = MockRender(); // <-- error here.
    injector = fixture.componentRef.injector;
  });

Expected vs actual behavior

Don't throw that error.

[jahusa02]

I noticed that as well.
It started with the flip of the default for standalone from false to true.
The logic how ng-mocks determines standalone components is the culprit I guess

[re-alam]

I've submitted a PR (#10583) to fix the "Forgot to flush TestBed?" error in Angular 19 when using MockRender.

If you've been experiencing this bug, please review the PR and let me know if it works for you.

[jeppetn]

Experiencing this as well, it's blocking our angular 19 upgrade.