The cycle is repeated for the model. Unit testing the view is usually impractical or impossible; thus, view code is left as "thin" and devoid of logic as possible (i.e. the view is a wrapper around widget library calls and presentation logic is contained in the presenter).
The process is repeated for the model. Typically, testing the view is not practical or achievable; consequently, view code is kept to a bare minimum and free from logic whenever feasible (i.e. the view serves primarily as an interface between widget library calls and presentation logic located in the presenter).