This project is read-only.

T4MVC Integration Tests

Jun 29, 2012 at 9:49 PM

I've been putting some thought into creating comprehensive integration tests for t4mvc since I've been bitten by the fallout of unrecognized changes. For instance, if I change the name of a action method, all views referenceing that action (such as Html.ActionLink("go here", MVC.Home.Index()) must be updated. This is dodgy since the views aren't checked against the compiler. Before I go and reinvent the wheel, does anyone know about any work being done to address this complication? Any ideas how this might best be achieved?


Jun 29, 2012 at 9:58 PM

There is a way to compile views, which catches these issues. e.g. see this post. Although it does slow down the build.

Note that this issue is not T4MVC specific. The difference is that in T4MVC, having a name mismatch gives you a compile error, while without T4MVC you get a runtime issue.