Striving to make views very simple through MV* patterns often removes a lot of the code from the view and leaves less room for failure. Theoretically, a good view only has wire up mechanisms to extract/present data and to forward commands. Beyond that you can look to frameworks that do integration testing to provide you with the tools to test views. I would also stress to be careful of the extent of testing you do here as it can become very expensive and result in brittle tests, especially if they are long running and often only are tested in a CI environment, say on a daily basis (highly likely chance people will break tests if they aren't constantly running them). A lot of people encourage simple smoke screen tests as the best ROI for testing the view layer. Thoughts?