Contents tagged with NUnit Add-In Help
-
Test With... Runtime
I thought I'd take a souvaneir snapshot before I repave. The final straw was installing .NET v2.0.31112. This is the runtime you get with the beta of Monad over at BetaPlace. Installing it in a virtual machine would have been sensible, but I was impatient.
-
Keyboard Shortcuts
[Xai comments] I just started using your tool and I have to say that I love it. Only one thing I'd improve, give us a keyboard shortcut! By that I mean let us know what we should map keyboard shortcuts to. For instance, I want to map a keyboard short cut to running tests on the solution. What command would I map it to? Or can I?
-
Lazy Update to NUnitAddIn-0.9.576d
Here is the lazy way to update to the latest version of NUnitAddIn.
-
Non-Admin & VS2005
I've had mixed success with the NUnitAddIn installation issues. I've tried to make it so that an administrator can do and install for all non-admin users. According to the documentation Visual Studio does supports this, but so far I haven't been able to get it working. I even created a noddy add-in using the 'Extensibility Project' wizard, but even this wouldn't work for non-admin users. Are there any add-ins out there that work for non-admin users?
-
Changing a DLL Project to EXE
NUnit supports having a '.config' file associated with a test assembly. When creating a new app domain, NUnit looks for a file with the same file name as the test assembly but ending with '.config' (eg My.Tests.dll.config). This is similar to the way .NET uses EXE.config files when a new process is started.
-
App.config Files
Kiwidude asked a question about how 'app.config' files are handled.
-
Abstract Test Pattern
I thought now would be a good time to mention NUnitAddin's support for 'Abstract Tests'. Jonathan de Halleux has a good write up where he compares the Abstract Test Pattern with MbUnit's support for Composite Unit Testing. I'm working with him to add support for MbUnit and will mention here when it's ready. For the moment this is what you can do with plain old NUnit...
-
Spelunking with Ad Hoc Tests
Here's a screenshot showing how easy it is to start spelunking about using Ad Hoc tests. In the example below I've defined a class that creates and disposes of an app domain. All the Ad Hoc test does is return the AppDomain object (which dumps all of its fields and properties). If an Ad Hoc test method is static - the constructor and dispose methods won't be called. Ad Hoc test methods can be private (you won't have to modify your code). At the moment methods with parameters aren't supported. A future version may pop up a dialog box for the parameters.