Why is the unit test useful when the view is not unit testable in MVVM?
- by BigTiger
Why is the unit test useful when the view is not unit testable in MVVM?
In MVVM, we have the models, view-models, and views. The claimed advantage is that MVVM can make the models and view=models unit testable. But all the three parties belong to the same application. If the views are not unit testable, why test the other two? Will unit testing the other two and leave one not tested improve the quality?
Removing all the code-behind from the views sounds weird to me. How about the code-behind only handles the pure UI operations?