Register now or log in to join your professional community.
The Model-View-ViewModel design pattern claims to aid separation of the View and the Business Logic in the GUI. What is it all about and how does it achieve separation of the GUI to enable better unit testing?
The view model in the MVVM pattern exposes both properties for the data to be displayed in the UI and operations on the data that can be invoked from the UI. An MVVM view model has no notion that a view (or any specific UI technology) exists. An MVVM view uses the binding feature to bidirectionally associate properties exposed by controls in the view (items in a drop-down menu) with the properties exposed by the view model.
With the concept that the model/view has not notion about each other, it is really easy to write a unit test.
Do you need help in adding the right keywords to your CV? Let our CV writing experts help you.