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 typically involves testing the model again for the view. Usually, it's not practical or feasible to test the view; therefore, view code is kept minimal and free from logic whenever possible (i.e. the view serves primarily as an interface between widget library calls and presentation logic housed in the presenter).