Bug: Erroneous test setup due to the usage of contentChildren

[LukasMachetanz]

Description of the bug

Let's assume having a component SystemUnderTestComponent as the SUT. This component internally renders ActionsComponent, which will be mocked within the test setup. ActionsComponent uses the new API contentChildren for accessing its content children. Unfortunately this API causes problems for SystemUnderTestComponent as the following error is thrown: TypeError: Cannot read properties of undefined (reading 'Symbol(SIGNAL)').

An example of the bug

https://codesandbox.io/p/sandbox/competent-fermat-llrjgt?file=%2Fsrc%2Ftest.spec.ts%3A35%2C35

Expected behavior

I would expect that the tests of SystemUnderTestComponent are not influenced by internals of the mocked component ActionsComponent.

Maybe this behavior is caused by the fact that ActionsComponent is mocked and Angular can't find ActionComponent?

[andreandersson]

Possibly duplicate of https://github.com/help-me-mom/ng-mocks/issues/8634

[LukasMachetanz]

@andreandersson, definitely. I experienced the same problem with viewChild as well.

[LukasMachetanz]

Any news on this issue? This bug really prevents using the new API.

[PieterjanDeClippel]

Same here. It seems that @ContentChildren(...) still works fine, but contentChildren(...) throws mentioned exception

@satanTime Any idea?

[wall-street-dev]

@PieterjanDeClippel has created a minimal repro here: https://github.com/PieterjanDeClippel/signaltesting/tree/master/src/app As mentioned by others, the issue arises when we use for example: MockDirective(BsCheckboxGroupDirective) and the BsCheckboxGroupDirective is using the new signal based queries.

[squelix]

Any news on this issue?

[wall-street-dev]

Any news on this issue?

A workaround in the meantime... 😕 https://stackoverflow.com/a/78736480/1277159