I am down in London for the first two days of the Microsoft TechDays event. First day has been very interesting, there seems to be a good buzz over the new testing features. So it looks good for my session tomorrow when I will be presenting on Lab Manager hope to see you there.
When I tried to run a working Ivonna test, previously targeted at .NET 3.5, against .NET 4 I found my test failing with the error -—– Test started: Assembly: Webpart.Tests.dll —— Bad Request Setup information Physical Web path: C:ProjectsTestTypeMockSampleTestWebSite Actual path: C:UsersfezAppDataLocalTempTemporary ASP.NET Filesroot156567f2 Turns out that the fix to simple, you have to use an absolute path i.e. the / in front of the BasicTest.aspx is vital \[TestMethod, Isolated\] public void LoadWebPage\_HelloWorldWebPart\_NoError() { TestSession session = new TestSession(); //Start each test with this WebRequest request = new WebRequest("/BasicTest....
Whilst preparing for my session at Techdays I have upgraded my 2010 Beta2 Lab Manager to RC. I am pleased to say the process is far more straight forward than the initial install. Again I used the Lab Manager team blog as my guide, they have revised ‘Getting started with Lab Management 2010 RC’ Parts 1, 2 ,3 and 4 posts to help. I was able to skip through the initial OS/VMM setup as this has not altered....
I was at the AIC 2010 conference yesterday, which I enjoyed more than last year. The most interesting session was Ivar Jacobson. He discussed how immature our industry is, with its disjoint between software engineers and academic computer scientists. Something I have commented on before when discussing if our industry should be licensed. He discussed how we need to build our industry upon commonly agreed kernel of simple best practice activities, not upon some currently fashionable process whether it be Waterfall, CMMI, Agile, Lean etc....
In 2008 I wrote a post Running Fitnesse.NET tests using MSTest. Recently I had need to us this technique on a VS2010 project, and as is so often the issue the code that worked then does not seem to work now. All I can assume is that the Fitnesse API had altered, but I thought I was using the same assemblies! So I pulled down the code from http://sourceforge.net/projects/fitnessedotnet/ and had a poke about....