Visual Studio Testing: Enough is enough

time to read 2 min | 202 words

I’ve blogged before about the problems that I’ve found in Visual Studio 2005 Testing Framework. Nevertheless, I tried to keep using it in a project where the advanced testing features weren’t needed. As I’ve said, it has some really nice UI, but the underlying engine just isn’t ready for general use.

Take for example the most recent hurdle: “Test Run deployment issue: The location of the file or directory ‘E:\Project\Bin\Debug\NHibernate.dll’ is not trusted” I fuzzed with it for a couple of hours, trying to convince it that it’s all right to run this code. Just to clarify, E: is a hard disk on the local system, and the CLR permissions are the same, meaning FullTrust for anything from this computer. NHibernate.dll is also strongly named, so it can’t be that.

I finally given up and moved back to trust NUnit, and I don’t think that I’ll look back. I feel a tremendous boost in speed (~30 seconds to ~5 seconds) when running the tests. I get easy way to run a single test, just about perfect!

I’m running inside a VM, and VSTS is still not RTM, so it may improve by that time, but I seriously doubt it.