[Bug]: input.required signals cannot be set in TestBed

[vbraun]

Version

14.0.3

Steps to reproduce

In your component, declare a required input signal:

@Component({ ... })
export class MyComponent {
    readonly data = input.required<MyData>();
}

and try to set it in the accompanying component.spec.ts:

    const myData: MyData = { ... }; 

    beforeEach(() => {
        fixture = TestBed.createComponent(MyComponent);
        fixture.componentRef.setInput('data', myData);
        component = fixture.componentInstance;
        fixture.detectChanges();
    });

Tests then fail with Can't set value of the 'data' input on the 'MyComponent' component.

If I change the input signal to not be required (i.e. just data = input<MyData>();) then the tests succeed.

Expected behavior

Tests should work ;)

Actual behavior

  console.error
    NG0303: Can't set value of the 'data' input on the 'MyComponent' component. Make sure that the 'data' property is annotated with @Input() or a mapped @Input('data') exists.

    > 70 |         fixture.componentRef.setInput('data', myData);

Additional context

Support for input signals was added in #2246

Using non-required signal input works, only the input.required signal fails.

Environment

$ npx envinfo --preset jest

  System:
    OS: Linux 6.7 Fedora Linux 39 (Workstation Edition)
    CPU: (24) x64 AMD Ryzen 9 7900X 12-Core Processor
  Binaries:
    Node: 20.12.0 - /usr/bin/node
    npm: 10.5.0 - /usr/bin/npm
  npmPackages:
    jest: ^29.5.0 => 29.5.0

[tunibjork]

Found this workaround in stack overflow:

    const myData: MyData = { ... }; 

    beforeEach(() => {
        fixture = TestBed.createComponent(MyComponent);
        component = fixture.componentInstance;
        TestBed.runInInjectionContext(() => {
            component.data = input(myData);
        });
        fixture.detectChanges();
    });

[markusahrweileramcon]

Does not work for me in 14.1.0

[ahnpnl]

@markusahrweileramcon we added example at

jest-preset-angular/examples/example-app-v17/src/app/dashboard/dashboard-hero.component.ts

Line 22 in c1e3ad7

hero = input.required<Hero>();

which runs on our CI. You can take a look

Oh I might miss the context, look like it's not the issue of this repo but rather than the issue of TestBed itself.

[ahnpnl]

Actually it works in the test via this line

jest-preset-angular/examples/example-app-v17/src/app/dashboard/dashboard-hero.component.spec.ts

Line 31 in c1e3ad7

fixture.componentRef.setInput('hero', expectedHero);

[markusahrweileramcon]

oh, my ... the issue was, that I've set the input in the tests itself and called detectChanges in the beforeEach
So the default test setup created by angular is not designed to work with inputs, which are not set initially in the beforeEach