Add value to MockComponent about ng-mocks HOT 6 CLOSED

then there's no reason to change code in the library, you can assert value by expect(component.writeValue).toHaveBeenCalledWith(expectedValue). The idea of mocks is to isolate the behavior of the object you want to replace the other objects by mocks that simulate the behavior of the real objects. And how to simulate the behavior should be defined by developer, not by library. So if you want to set value property when writeValue has been called you should use callFake to achieve your goals.

from ng-mocks.

Hi,

are you sure you shouldn't assert call of writeValue with proper arguments?

from ng-mocks.

@satanTime, this was written as a state test, I don't see value in checking writeValue call because the end result is what I'm interested in, not how it's achieved. Feel free to add any other asserts or tests if that's part of the pattern you follow. I just want it to be in release so that tests from parent component that verify custom components value from form is possible (check formControl bindings)

from ng-mocks.

Could you provide code of exact test case you try to solve?

from ng-mocks.

@satanTime, it's the one that's in the PR

from ng-mocks.

Really, that makes perfect sense. :)
Consider the issue to be closed then.

from ng-mocks.