<p>I am currently building an application using ASP.NET MVC.  The data entry pages are fairly easy to code, I just make the Model for the page of the type of my business object:</p>

<pre><code>namespace MyNameSpace.Web.Views.ProjectEdit
{
    public partial class MyView : ViewPage&lt;Project&gt;
    {
    }
}
</code></pre>

<p>Where I am struggling is figuring out the best way to implement a dashboard like interface, with stand-alone parts, using ASP.NET MVC, where the Model for each part would be different? I'm <strong>assuming</strong> that each part would be an MVC user control.  </p>

<p>Also, how could I make it so each part is testable?</p>

I think that user controls is probably the way to go.  I'm not sure what the concern is about testability.  You should be able to test that your controller is providing the right view data -- since you'll have several models each of these will probably be stored in a separate view data item, rather than aggregating them in a single model.  Aggregating in a single model is also possible, although probably more brittle.  Each control would just need to check for a particular view data item, rather than being specific to a particular model.  You could approximate the model variable on each view page by doing:
```
```
<% MyUserControlModel model = ViewData["MyUserControlModel"]
         as MyUserControlModel; %>

<div id="myUserControl_dashboard" class="dashboard">
   Name: <%= model.Name %><br />
   Count: <%$ model.Count %>
</div>
```
```
If you need to test your view, then you're probably already using Selenium or some other web testing framework.  I don't think that these would care how the page was constructed and you should be able to construct your tests pretty much like you always do.