A late reminder but tonight is the monthly Agile Yorkshire meeting. This month is an open floor meeting with short presentations from members. Currently the planned subjects are: REST and OpenRasta Silverlight F# Thoughts on Test Driven Development practices Behaviour Driven Development Hope to see you there, usual place usual time (Victoria Hotel, 28 Great George St, Leeds. See here for directions, 7pm)
I have got round to watching Peli de Halleux’s presentation on testing SharePoint with moles from the SharePoint Connections 2010 event in Amsterdam, very interesting. This brings a whole new set of tools to the testing of Sharepoint. I think it is best to view the subject of this presentation in two parts Pex and Moles, even though they are from the same stable; Moles being produced to enable Pex. But rather than me explaining how it all works just watch the video....
I was doing some work today where I needed to fake out a SPWeb object. No problem you think, I am using Typemock Isolator so I just use the line var fakeWeb = Isolate.Fake.Instance(); But I got the error Microsoft.SharePoint.SPWeb.SPWebConstructor(SPSite site, String url, Boolean bExactWebUrl, SPRequest request) Microsoft.SharePoint.SPWeb..ctor(SPSite, site, String url) eo.CreateFakeInstance[T](Members behavior, Constructor constructorFlag, Constructor baseConstructorFlag, Type baseType, Object[] ctorArgs) eo.Instance[T](Members behavior) (Points to the SPWeb web line as source of error)...
I have at last worked all the way through setting up my portable end to end demo of testing using Windows Test and Lab Manager. The last error I had to resolve was the tests not running in the lab environment (though working locally on the development PC). My the Lab Workflow build was recorded as a partial success i.e. it built, it deployed but all the tests failed. I have not found a way to see the detail of why the tests failed in VS2010 Build Explorer....
I have been looking at TFS 2010 Lab Manager recently. One problem I had was that using the sample code from the Lab Manager Blog Walkthru the building of the CALC ASP.NET web site failed on the build server, I got an error ASPNETCOMPILER: error 1003 The directory ‘c:build1LabWalkthruCalculator –BuildCalc’ does not exist. and the build service was right it didn’t exist; it should have been ‘c:build1LabWalkthruCalculator –BuildSourceCalc’. This was due to a problem detailed here....