[ewerton336]

MatInputHarness.setValue updates the value by clearing the input, sending keys and setting the
value property, but it never dispatches a change event. As a result, (change) listeners on a
matInput aren't invoked in tests, even though the value changed (see the reproduction in the issue).

This change dispatches a change event at the end of setValue, which is consistent with what
MatDatepickerInputHarness.setValue already does (#20877). A unit test was added that fails without
the fix.

Fixes #30160

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[ewerton336]

I signed it!

[crisbeto]

I think this was intentional, because if I remember correctly, the change event gets dispatched when the user blurs the input.

[ewerton336]

Thanks for taking a look! That makes sense for real user interaction, since change fires when the value is committed/blurred. The reason I went this way is that MatDatepickerInputHarness.setValue already dispatches change at the end (from #20877), so the two input harnesses currently behave differently, and with MatInputHarness tests that listen to (change) have to call blur() explicitly after setValue.

If you'd rather keep the current behavior, I'm happy to close this, or alternatively update the setValue docs to mention that blur() is needed to trigger change. Whatever you prefer.