Permalink
Browse files

Adding nunit files (both assemblies and executables) to Tools.

SVN: trunk@4377
  • Loading branch information...
1 parent 7d32ad6 commit f368dd2ff74db8f1e6361816a59db17de5dcc8b8 Tuna Toksoz committed May 24, 2009
Showing with 11,008 additions and 0 deletions.
  1. +277 −0 Tools/nunit/NUnitFitTests.html
  2. +84 −0 Tools/nunit/NUnitTests.config
  3. +14 −0 Tools/nunit/NUnitTests.nunit
  4. +4 −0 Tools/nunit/agent.conf
  5. +18 −0 Tools/nunit/agent.log.conf
  6. +96 −0 Tools/nunit/clr.bat
  7. BIN Tools/nunit/framework/nunit.framework.dll
  8. +9,803 −0 Tools/nunit/framework/nunit.framework.xml
  9. BIN Tools/nunit/framework/nunit.mocks.dll
  10. BIN Tools/nunit/framework/pnunit.framework.dll
  11. +18 −0 Tools/nunit/launcher.log.conf
  12. BIN Tools/nunit/lib/Failure.jpg
  13. BIN Tools/nunit/lib/Gray.jpg
  14. BIN Tools/nunit/lib/Ignored.jpg
  15. BIN Tools/nunit/lib/Success.jpg
  16. BIN Tools/nunit/lib/fit.dll
  17. BIN Tools/nunit/lib/log4net.dll
  18. BIN Tools/nunit/lib/nunit-console-runner.dll
  19. BIN Tools/nunit/lib/nunit-gui-runner.dll
  20. BIN Tools/nunit/lib/nunit.core.dll
  21. BIN Tools/nunit/lib/nunit.core.interfaces.dll
  22. BIN Tools/nunit/lib/nunit.fixtures.dll
  23. BIN Tools/nunit/lib/nunit.uiexception.dll
  24. BIN Tools/nunit/lib/nunit.uikit.dll
  25. BIN Tools/nunit/lib/nunit.util.dll
  26. BIN Tools/nunit/nunit-agent.exe
  27. +87 −0 Tools/nunit/nunit-agent.exe.config
  28. BIN Tools/nunit/nunit-console-runner.dll
  29. BIN Tools/nunit/nunit-console-x86.exe
  30. +87 −0 Tools/nunit/nunit-console-x86.exe.config
  31. BIN Tools/nunit/nunit-console.exe
  32. +87 −0 Tools/nunit/nunit-console.exe.config
  33. BIN Tools/nunit/nunit-x86.exe
  34. +95 −0 Tools/nunit/nunit-x86.exe.config
  35. BIN Tools/nunit/nunit.core.dll
  36. BIN Tools/nunit/nunit.core.interfaces.dll
  37. BIN Tools/nunit/nunit.exe
  38. +95 −0 Tools/nunit/nunit.exe.config
  39. BIN Tools/nunit/nunit.framework.dll
  40. BIN Tools/nunit/nunit.util.dll
  41. BIN Tools/nunit/pnunit-agent.exe
  42. +87 −0 Tools/nunit/pnunit-agent.exe.config
  43. BIN Tools/nunit/pnunit-launcher.exe
  44. +87 −0 Tools/nunit/pnunit-launcher.exe.config
  45. BIN Tools/nunit/pnunit.framework.dll
  46. BIN Tools/nunit/pnunit.tests.dll
  47. BIN Tools/nunit/runFile.exe
  48. +43 −0 Tools/nunit/runFile.exe.config
  49. +2 −0 Tools/nunit/runpnunit.bat
  50. +24 −0 Tools/nunit/test.conf
@@ -0,0 +1,277 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+ <body>
+ <h1>NUnit Acceptance Tests</h1>
+ <p>
+ Developers love self-referential programs! Hence, NUnit has always run all it's
+ own tests, even those that are not really unit tests.
+ <p>Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's
+ FIT framework. At this time, the tests are pretty rudimentary, but it's a start
+ and it's a framework for doing more.
+ <h2>Running the Tests</h2>
+ <p>Open a console or shell window and navigate to the NUnit bin directory, which
+ contains this file. To run the test under Microsoft .Net, enter the command
+ <pre> runFile NUnitFitTests.html TestResults.html .</pre>
+ To run it under Mono, enter
+ <pre> mono runFile.exe NUnitFitTests.html TestResults.html .</pre>
+ Note the space and dot at the end of each command. The results of your test
+ will be in TestResults.html in the same directory.
+ <h2>Platform and CLR Version</h2>
+ <table BORDER cellSpacing="0" cellPadding="5">
+ <tr>
+ <td colspan="2">NUnit.Fixtures.PlatformInfo</td>
+ </tr>
+ </table>
+ <h2>Verify Unit Tests</h2>
+ <p>
+ Load and run the NUnit unit tests, verifying that the results are as expected.
+ When these tests are run on different platforms, different numbers of tests may
+ be skipped, so the values for Skipped and Run tests are informational only.
+ <p>
+ The number of tests in each assembly should be constant across all platforms -
+ any discrepancy usually means that one of the test source files was not
+ compiled on the platform. There should be no failures and no tests ignored.
+ <p><b>Note:</b>
+ At the moment, the nunit.extensions.tests assembly is failing because the
+ fixture doesn't initialize addins in the test domain.
+ <p>
+ <table BORDER cellSpacing="0" cellPadding="5">
+ <tr>
+ <td colspan="6">NUnit.Fixtures.AssemblyRunner</td>
+ </tr>
+ <tr>
+ <td>Assembly</td>
+ <td>Tests()</td>
+ <td>Run()</td>
+ <td>Skipped()</td>
+ <td>Ignored()</td>
+ <td>Failures()</td>
+ </tr>
+ <tr>
+ <td>nunit.framework.tests.dll</td>
+ <td>397</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.core.tests.dll</td>
+ <td>355</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.util.tests.dll</td>
+ <td>238</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.mocks.tests.dll</td>
+ <td>43</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.extensions.tests.dll</td>
+ <td>5</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit-console.tests.dll</td>
+ <td>40</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.uikit.tests.dll</td>
+ <td>34</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit-gui.tests.dll</td>
+ <td>15</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>nunit.fixtures.tests.dll</td>
+ <td>6</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ </table>
+ <h2>Code Snippet Tests</h2>
+ <p>
+ These tests create a test assembly from a snippet of code and then load and run
+ the tests that it contains, verifying that the structure of the loaded tests is
+ as expected and that the number of tests run, skipped, ignored or failed is
+ correct.
+ <p>
+ <table BORDER cellSpacing="0" cellPadding="5">
+ <tr>
+ <td colspan="6">NUnit.Fixtures.SnippetRunner</td>
+ </tr>
+ <tr>
+ <td>Code</td>
+ <td>Tree()</td>
+ <td>Run()</td>
+ <td>Skipped()</td>
+ <td>Ignored()</td>
+ <td>Failures()</td>
+ </tr>
+ <tr>
+ <td><pre>public class TestClass
+{
+}</pre>
+ </td>
+ <td>EMPTY</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td><pre>using NUnit.Framework;
+
+[TestFixture]
+public class TestClass
+{
+}</pre>
+ </td>
+ <td>TestClass</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td><pre>using NUnit.Framework;
+
+[TestFixture]
+public class TestClass
+{
+ [Test]
+ public void T1() { }
+ [Test]
+ public void T2() { }
+ [Test]
+ public void T3() { }
+}</pre>
+ </td>
+ <td><pre>TestClass
+&gt;T1
+&gt;T2
+&gt;T3</pre>
+ </td>
+ <td>3</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td><pre>using NUnit.Framework;
+
+[TestFixture]
+public class TestClass1
+{
+ [Test]
+ public void T1() { }
+}
+
+[TestFixture]
+public class TestClass2
+{
+ [Test]
+ public void T2() { }
+ [Test]
+ public void T3() { }
+}</pre>
+ </td>
+ <td><pre>TestClass1
+&gt;T1
+TestClass2
+&gt;T2
+&gt;T3</pre>
+ </td>
+ <td>3</td>
+ <td>0</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td><pre>using NUnit.Framework;
+
+[TestFixture]
+public class TestClass
+{
+ [Test]
+ public void T1() { }
+ [Test, Ignore]
+ public void T2() { }
+ [Test]
+ public void T3() { }
+}</pre>
+ </td>
+ <td><pre>TestClass
+&gt;T1
+&gt;T2
+&gt;T3</pre>
+ </td>
+ <td>2</td>
+ <td>0</td>
+ <td>1</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td><pre>using NUnit.Framework;
+
+[TestFixture]
+public class TestClass
+{
+ [Test]
+ public void T1() { }
+ [Test, Explicit]
+ public void T2() { }
+ [Test]
+ public void T3() { }
+}</pre>
+ </td>
+ <td><pre>TestClass
+&gt;T1
+&gt;T2
+&gt;T3</pre>
+ </td>
+ <td>2</td>
+ <td>1</td>
+ <td>0</td>
+ <td>0</td>
+ </tr>
+ </table>
+ <h2>Summary Information</h2>
+ <table BORDER cellSpacing="0" cellPadding="5">
+ <tr>
+ <td colspan="2">fit.Summary</td>
+ </tr>
+ </table>
+ </body>
+</html>
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<configuration>
+<!--
+ This is the configuration file for the NUnitTests.nunit test project. You may
+ need to create a similar configuration file for your own test project.
+ -->
+
+<!--
+ The <NUnit> section is only needed if you want to use a non-default value
+ for any of the settings. It is commented out below. If you are going to use
+ it, you must deifne the NUnit section group and the sections you need.
+
+ The syntax shown here works for most runtimes. If NUnit fails at startup, you
+ can try specifying the name of the assembly containing the NameValueSectionHandler:
+
+ <section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler, System" />
+
+ If that fails, try the fully qualified name of the assembly:
+
+ <section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler, System,
+ Version=2.0.50727.832, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
+
+ Unfortunately, this last approach makes your config file non-portable across runtimes.
+ -->
+
+<!--
+ <configSections>
+ <sectionGroup name="NUnit">
+ <section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler"/>
+ <section name="TestRunner" type="System.Configuration.NameValueSectionHandler"/>
+ </sectionGroup>
+ </configSections>
+ -->
+
+ <appSettings>
+ <!-- User application and configured property settings go here.-->
+ <!-- Example: <add key="settingName" value="settingValue"/> -->
+ <add key="test.setting" value="54321" />
+ </appSettings>
+
+<!-- Sample NUnit section group showing all default values -->
+<!--
+ <NUnit>
+ <TestCaseBuilder>
+ <add key="OldStyleTestCases" value="false" />
+ </TestCaseBuilder>
+ <TestRunner>
+ <add key="ApartmentState" value="MTA" />
+ <add key="ThreadPriority" value="Normal" />
+ </TestRunner>
+ </NUnit>
+-->
+
+ <!--
+ The following <runtime> section allows running nunit tests under
+ .NET 1.0 by redirecting assemblies. The appliesTo attribute
+ causes the section to be ignored except under .NET 1.0.
+ -->
+ <runtime>
+ <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"
+ appliesTo="v1.0.3705">
+ <dependentAssembly>
+ <assemblyIdentity name="System" publicKeyToken="b77a5c561934e089" culture="" />
+ <bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
+ </dependentAssembly>
+ <dependentAssembly>
+ <assemblyIdentity name="System.Data" publicKeyToken="b77a5c561934e089" culture="" />
+ <bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
+ </dependentAssembly>
+ <dependentAssembly>
+ <assemblyIdentity name="System.Drawing" publicKeyToken="b03f5f7f11d50a3a" culture="" />
+ <bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
+ </dependentAssembly>
+ <dependentAssembly>
+ <assemblyIdentity name="System.Windows.Forms" publicKeyToken="b77a5c561934e089" culture="" />
+ <bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
+ </dependentAssembly>
+ <dependentAssembly>
+ <assemblyIdentity name="System.Xml" publicKeyToken="b77a5c561934e089" culture="" />
+ <bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
+ </dependentAssembly>
+ </assemblyBinding>
+ </runtime>
+</configuration>
@@ -0,0 +1,14 @@
+<NUnitProject>
+ <Settings appbase="."/>
+ <Config name="Default" binpath="lib;tests;framework" runtimeFramework="v2.0">
+ <assembly path="tests/nunit.framework.tests.dll" />
+ <assembly path="tests/nunit.core.tests.dll" />
+ <assembly path="tests/nunit.util.tests.dll" />
+ <assembly path="tests/nunit.mocks.tests.dll" />
+ <assembly path="tests/nunit-console.tests.dll" />
+ <assembly path="tests/nunit.uiexception.tests.dll" />
+ <assembly path="tests/nunit.uikit.tests.dll" />
+ <assembly path="tests/nunit-gui.tests.dll" />
+ <assembly path="tests/nunit.fixtures.tests.dll" />
+ </Config>
+</NUnitProject>
View
@@ -0,0 +1,4 @@
+<AgentConfig>
+ <Port>8080</Port>
+ <PathToAssemblies>.</PathToAssemblies>
+</AgentConfig>
Oops, something went wrong.

0 comments on commit f368dd2

Please sign in to comment.