By default the NUnit installation program places all of the files into the C:\Program Files\NUnit 2.4.1 directory. In the installation directory there are three sub-directories: bin, doc, and samples. Source code is no longer provided with the binary installation package. Download the source package if source is needed.
The installation program places a number of items in the Start menu. There are a number of shortcuts, which run the NUnit GUI under various versions of .NET or under Mono, depending on the versions available on your system at the time of installation.
When running NUnit from the command line or through the desktop shortcut, the
configuration files files nunit.exe.config and nunit-console.exe.config control
which version of the CLR is used. As installed, the
Settings that you place in these files are not available to your tests or to the production code you are testing. A separate config file is used when running tests. If you are running tests from the test.dll assembly, the config file should be named test.dll.config. If you are running tests from the NUnit test project MyTests.nunit, the config file should be named MyTests.config. In either case the config file must reside in the same directory as the file from which it takes its name.
In addition to settings of your own, the config file for a set of tests may contain information used by NUnit in loading your tests. In particular, this allows you to control the apartment state and priority of the thread that NUnit uses to run your tests. Other settings may be added in the future. See the file nunit.tests.dll for an example.
Verify that the installation has worked successfully by running the NUnit gui and loading and running NUnitTests.nunit in the bin directory. All tests should pass.
Note: Although the NUnit installation has been modified to allow non-admin users to install, there are still a large number of tests which can only run successfully under an administrative id. This is a problem with the code in the tests themselves, not with NUnit.
The assembly timing-tests.dll contains several long-running tests that are used to verify that all remoting timeout problems have been fixed. The test cases all run for six to 12 minutes and give no indication whatsoever that they are working! This is required since correct handling of a non-communicative user test is what these tests are all about.
Additional tests are included with the samples and in separate assemblies used as data by the verification tests themselves. Failures or not run conditions in these tests are intentional.
If you are building NUnit from source, it is recommended that you use the NAnt script for your final build, since it puts all the required files into one directory, from which you can easily copy them. Perform a manual installation by following these steps:
Mono is delivered with a version of NUnit already pre-installed. The Mono 1.0 release included a beta version of NUnit 2.2. Later builds may include a more up-to-date version of NUnit. Before attempting to install NUnit under Mono, determine whether an equivalent or newer version is already installed. It may be necessary to remove the pre-installed version from the GAC in order for the new version to be recognized.