Broken tests for the components with setters in Input

[GlebIrovich]

Hey there! I noticed, that updating to 10.4.1 cause some of my tests failing. I investigated a bit and it seems, that the components, which are using setters in the inputs are not invoking logic that was in the setter before.

I assume it might be caused by this change in 10.2.1 which changes the way how component properties are added to the fixture:

angular-testing-library/projects/testing-library/src/lib/testing-library.ts

Line 203 in 4b6e491

function setComponentProperties<SutType>(

I am curios , is it a bug? And if not, what is the preferred way to test components which use set in the @Input?

[timdeschryver]

Oh shoot, it could be a bug.
It seems like we don't have any tests to cover this behavior, because it should "just" work.

Can you perhaps create PR with a fix, or a test with the expected behavior?

[GlebIrovich]

@timdeschryver thanks for clarification! I have no experience contributing to an open source project, but it seems like a sign to give a shot. I will prepare a PR with tests at least.

[timdeschryver]

Thank you in advance!
If it takes too long, or if you're having troubles feel free to ask for help, or just to paste the test here 🙂

[GlebIrovich]

here is a PR

Let me know if I missed anything

[github-actions]

🎉 This issue has been resolved in version 10.4.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀