Archives
-
Fragmenting of the testing tools market?
Darrel Norton asks
-
System.Testing
Peter Provost has started a petition to include unit testing support in all versions of Visual Studio 2005. While I agree that unit testing should be essential part of all development, I don't think Visual Studio is the place to introduce an important new API. I think a much more fitting place would be the BCL and SSCLI/Rotor. At the moment the BCL has an extensive set of unit tests. I would be in favor of converting these over to using a core testing framework (say 'System.Testing'). We would then have a standard API for writing tests under all implementations of the CLI. I think this is where real value would come.
-
Visual Studio 2002, 2003 & 2005
It is getting there. Your feedback particularly welcome if you're trying it with Visual Studio 2002 or 2005. If it fails to load when Visual Studio first starts - check the left hand box in 'Add-in Manager' next to 'NUnit Add-In'. Make sure it's the left hand one, you don't want it loading on startup!
-
NUnitAddIn & VS.NET 2002
Having difficulty installing the Add-In into VS.NET 2002 - is it supported? The add-in appears, but when I turn it on I get 'The Add-in 'NUnit Add-In' failed to load..... Error Number: 80131534 - does that mean anything to anyone? Would upgrade, but we have too many systems to upgrade and are at a critical point in development - shame 2003's project files are not backward compatibal eh!