Open Source projects that ship with unit tests based on NUnit also usually ship the NUnit runners and accompanying binaries. For NUnit 2.4.8, distributing its bin directory verbatim with the actual project amounts to 46 files and a blank addins directory. What would be the minimum set of files needed if all one wanted was to distribute the GUI and console runners along with the base nunit.framework.dll required for authoring tests (and without the mocking infrastructure)?
For reference, the NUnit 2.4.8 bin directory looks like this:
- addins/
- clr.bat
- failure.jpg
- fit.dll
- ignored.jpg
- loadtest-assembly.dll
- mock-assembly.dll
- nonamespace-assembly.dll
- notestfixtures-assembly.dll
- nunit.core.dll
- nunit.core.extensions.dll
- nunit.core.interfaces.dll
- nunit.core.tests.dll
- nunit.exe
- nunit.exe.config
- nunit.extensions.tests.dll
- nunit.fixtures.dll
- nunit.fixtures.tests.dll
- nunit.framework.dll
- nunit.framework.extensions.dll
- nunit.framework.tests.dll
- nunit.framework.xml
- nunit.mocks.dll
- nunit.mocks.tests.dll
- nunit.uikit.dll
- nunit.uikit.tests.dll
- nunit.util.dll
- nunit.util.tests.dll
- nunit-console.exe
- nunit-console.exe.config
- nunit-console.tests.dll
- nunit-console-runner.dll
- nunit-console-x86.exe
- nunit-console-x86.exe.config
- NUnitFitTests.html
- nunit-gui.tests.dll
- nunit-gui-runner.dll
- NUnitTests.config
- NUnitTests.nunit
- nunit-x86.exe
- nunit-x86.exe.config
- runFile.exe
- runFile.exe.config
- success.jpg
- test-assembly.dll
- test-utilities.dll
- timing-tests.dll
Best Answer
I can successfully run tests with only the following 6 NUnit files present: