Mocking a Standalone Component without a Selector does not mock the imports

[Simon-TheHelpfulCat]

A minimal reproduction:

import { CommonModule } from "@angular/common";
import { Component } from "@angular/core";
import { RouterModule } from "@angular/router";
import { MockBuilder, MockRender } from "ng-mocks";

@Component({
  selector: "my-test-one",
  standalone: true,
  imports: [CommonModule, RouterModule],
  template: `<a [routerLink]="['test']">Test</a>`
})
class TestOneComponent {}

@Component({
  standalone: true,
  imports: [CommoBoth ytestsnModule, RouterModule],
  template: `<a [routerLink]="['test']">Test</a>`
})
class TestTwoComponent {}

describe("with selector", () => {
  beforeEach(() => MockBuilder(TestOneComponent));

  it("should render", () => {
    expect(MockRender(TestOneComponent).point.componentInstance).toBeDefined();
  });
});

describe("witout selector", () => {
  beforeEach(() => MockBuilder(TestTwoComponent));

  it("should render", () => {
    expect(MockRender(TestTwoComponent).point.componentInstance).toBeDefined();
  });
});

Both tests pass, but looking in the console you see:

NG0303: Can't bind to 'routerLink' since it isn't a known property of 'a' (used in the 'MockMiddlewareTestTwoComponent' component template).

Adding a selector to TextTwoComponent or adding .mock(RouterModule)) to the MockBuilder removes this message.

This minimal reproduction is reproduced in Code Sandbox.

[satanTime]

Hi @Simon-TheHelpfulCat,

thanks for the report!

[satanTime]

v14.3.2 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.