lCleanup[useCaptureOrSubIdx] is not a function / view.disposables[i] is not a function

[satanTime]

There's an interesting case that throws an error.

min project: ng-routing-test

The structure of the project should be like in the code sample above.

[satanTime]

The issue is caused by (click)="..." in app.component.html, if to remove all of them there's no the issue.
For now I would assume that the problem is in angular itself, but still deeper investigation is required.

[satanTime]

Here is app folder that can be used in e2e app.zip

[satanTime]

The error is thrown only on 2+ execution of beforeEach, looks like there's a new cache inside of TestBed that should be reset in ngMocks.flushTestBed().

[satanTime]

The min test to reproduce the issue.

import { Component, NgModule } from '@angular/core';
import { TestBed } from '@angular/core/testing';
import { BrowserModule } from '@angular/platform-browser';
import { MockBuilder, MockRender } from 'ng-mocks';

@Component({
  selector: 'app-root',
  template: `<a (click)="title = 'test'">click</a>`,
})
export class AppComponent {
  title = 'ng-routing-test';
}

@NgModule({
  bootstrap: [AppComponent],
  declarations: [AppComponent],
  imports: [BrowserModule],
  providers: [],
})
export class AppModule {}

fdescribe('issue-162', () => {
  beforeEach(() => MockBuilder(AppComponent, AppModule));

  // triggers the error.
  afterEach(() => TestBed.resetTestingModule());

  it(`checks title`, () => {
    const fixture = MockRender(AppComponent);
    expect(fixture.point.componentInstance.title).toEqual('ng-routing-test');
  });
});

It only affects already existing components that belong to another module, if a new component is created at runtime then everything is fine and the error doesn't appear.

[satanTime]

The problem is caused by mocked version of EventManager.addEventListener from BrowserModule.