I had an enjoyable day at Developer Day Scotland in Glasgow yesterday; a big thank you to the organisers and speakers. I did a short grok talk on ‘Testing Sharepoint using Typemock Isolator and Ivonna’, a few people asked me for more details. Well the session was based on a post I did a while ago. I have updated that post to tidy a couple of issue I found whilst preparing the session....
The MVC framework provides an excellent way to create a testable web site. In fact when you create a new MVC project you are given the option to create an associated test project that contains MSTEST unit tests for all the sample methods in the MVC Controller class; which you can add to as you go along. Recently whilst working on an MVC project I noticed that the one area that this model does not let you test is that of access control....
I will be speaking on developer testing of SharePoint projects using Typemock at both the Birmingham and Manchester NXtGen user groups in August. For more details check the NxtGen site.
Like a good developer I have been trying to run Visual Studio with least privilege; with Windows 7 this seems to work well. My main account is not an administrator, but Windows prompts me for elevated rights when needed. I have been developing happily with Visual Studio and Typemock without any need for extra rights. However, when I have been doing some testing using Ivonna, the Typemock add-in, I hit a problem....
I recently re-enabled feature on a ASP.NET site. This feature (a set of pages) had been running OK about six months ago for an initial pilot project but was disabled until now until a decision was made to develop the feature fully. In intervening time the web site had other modification and had been rebuilt (it was targeted at .NET 3.5) without issue. When I re-enabled the feature (renamed a ....