nunit 2.4.8.0
Sign up to get free protection for your applications and to get access to all the features.
- data/docs/addinsDialog.html +74 -0
- data/docs/assertions.html +91 -0
- data/docs/attributes.html +89 -0
- data/docs/category.html +265 -0
- data/docs/classicModel.html +92 -0
- data/docs/codeFuncs.js +77 -0
- data/docs/collectionAssert.html +162 -0
- data/docs/collectionConstraints.html +130 -0
- data/docs/comparisonAsserts.html +271 -0
- data/docs/comparisonConstraints.html +109 -0
- data/docs/compoundConstraints.html +97 -0
- data/docs/conditionAsserts.html +123 -0
- data/docs/conditionConstraints.html +106 -0
- data/docs/configEditor.html +93 -0
- data/docs/configFiles.html +155 -0
- data/docs/consoleCommandLine.html +271 -0
- data/docs/constraintModel.html +134 -0
- data/docs/contextMenu.html +106 -0
- data/docs/culture.html +255 -0
- data/docs/customAsserts.html +115 -0
- data/docs/customConstraints.html +101 -0
- data/docs/description.html +178 -0
- data/docs/equalConstraint.html +139 -0
- data/docs/equalityAsserts.html +187 -0
- data/docs/exception.html +296 -0
- data/docs/explicit.html +256 -0
- data/docs/extensibility.html +83 -0
- data/docs/favicon.ico +0 -0
- data/docs/features.html +75 -0
- data/docs/fileAssert.html +114 -0
- data/docs/files/QuickStart.Spanish.doc +0 -0
- data/docs/files/QuickStart.doc +0 -0
- data/docs/files/Results.xsd +70 -0
- data/docs/files/Summary.xslt +47 -0
- data/docs/files/TestResult.xml +103 -0
- data/docs/files/Thumbs.db +0 -0
- data/docs/fixtureSetup.html +201 -0
- data/docs/fixtureTeardown.html +204 -0
- data/docs/getStarted.html +80 -0
- data/docs/guiCommandLine.html +183 -0
- data/docs/identityAsserts.html +99 -0
- data/docs/ignore.html +249 -0
- data/docs/img/addinsDialog.JPG +0 -0
- data/docs/img/assembliesTab.jpg +0 -0
- data/docs/img/assemblyReloadOptions.JPG +0 -0
- data/docs/img/bulletOff.gif +0 -0
- data/docs/img/bulletOn.gif +0 -0
- data/docs/img/configEditor.jpg +0 -0
- data/docs/img/console-mock.jpg +0 -0
- data/docs/img/displayTab.jpg +0 -0
- data/docs/img/generalOptions.jpg +0 -0
- data/docs/img/generalTab.jpg +0 -0
- data/docs/img/gui-screenshot.jpg +0 -0
- data/docs/img/gui-verify.jpg +0 -0
- data/docs/img/langFilter.gif +0 -0
- data/docs/img/logo.gif +0 -0
- data/docs/img/miniGui.jpg +0 -0
- data/docs/img/optionsDialog.jpg +0 -0
- data/docs/img/resultTab.jpg +0 -0
- data/docs/img/testLoadOptions.jpg +0 -0
- data/docs/img/testOutputOptions.jpg +0 -0
- data/docs/img/testProperties.jpg +0 -0
- data/docs/img/testResultOptions.JPG +0 -0
- data/docs/img/testTab.jpg +0 -0
- data/docs/img/testsTab.JPG +0 -0
- data/docs/img/textOutputOptions.jpg +0 -0
- data/docs/img/treeDisplayOptions.JPG +0 -0
- data/docs/img/visualStudioOptions.JPG +0 -0
- data/docs/index.html +75 -0
- data/docs/installation.html +172 -0
- data/docs/license.html +88 -0
- data/docs/listMapper.html +100 -0
- data/docs/mainMenu.html +260 -0
- data/docs/multiAssembly.html +130 -0
- data/docs/nunit-console.html +84 -0
- data/docs/nunit-gui.html +115 -0
- data/docs/nunit.css +118 -0
- data/docs/nunitAddins.html +331 -0
- data/docs/optionsDialog.html +262 -0
- data/docs/platform.html +285 -0
- data/docs/platformSupport.html +99 -0
- data/docs/projectEditor.html +127 -0
- data/docs/property.html +219 -0
- data/docs/propertyConstraint.html +89 -0
- data/docs/quickStart.html +314 -0
- data/docs/releaseNotes.html +1235 -0
- data/docs/sameasConstraint.html +98 -0
- data/docs/samples.html +126 -0
- data/docs/setCulture.html +173 -0
- data/docs/setup.html +199 -0
- data/docs/setupFixture.html +198 -0
- data/docs/stringAssert.html +107 -0
- data/docs/stringConstraints.html +111 -0
- data/docs/suite.html +222 -0
- data/docs/teardown.html +204 -0
- data/docs/test.html +171 -0
- data/docs/testFixture.html +168 -0
- data/docs/testProperties.html +76 -0
- data/docs/typeAsserts.html +101 -0
- data/docs/typeConstraints.html +103 -0
- data/docs/upgrade.html +97 -0
- data/docs/utilityAsserts.html +108 -0
- data/docs/vsSupport.html +140 -0
- data/lib/net-1.1/Failure.jpg +0 -0
- data/lib/net-1.1/Ignored.jpg +0 -0
- data/lib/net-1.1/NUnitFitTests.html +277 -0
- data/lib/net-1.1/NUnitTests.config +84 -0
- data/lib/net-1.1/NUnitTests.nunit +14 -0
- data/lib/net-1.1/Success.jpg +0 -0
- data/lib/net-1.1/clr.bat +96 -0
- data/lib/net-1.1/fit.dll +0 -0
- data/lib/net-1.1/loadtest-assembly.dll +0 -0
- data/lib/net-1.1/mock-assembly.dll +0 -0
- data/lib/net-1.1/nonamespace-assembly.dll +0 -0
- data/lib/net-1.1/notestfixtures-assembly.dll +0 -0
- data/lib/net-1.1/nunit-console-runner.dll +0 -0
- data/lib/net-1.1/nunit-console.exe +0 -0
- data/lib/net-1.1/nunit-console.exe.config +117 -0
- data/lib/net-1.1/nunit-console.tests.dll +0 -0
- data/lib/net-1.1/nunit-gui-runner.dll +0 -0
- data/lib/net-1.1/nunit-gui.tests.dll +0 -0
- data/lib/net-1.1/nunit.core.dll +0 -0
- data/lib/net-1.1/nunit.core.extensions.dll +0 -0
- data/lib/net-1.1/nunit.core.interfaces.dll +0 -0
- data/lib/net-1.1/nunit.core.tests.dll +0 -0
- data/lib/net-1.1/nunit.exe +0 -0
- data/lib/net-1.1/nunit.exe.config +121 -0
- data/lib/net-1.1/nunit.extensions.tests.dll +0 -0
- data/lib/net-1.1/nunit.fixtures.dll +0 -0
- data/lib/net-1.1/nunit.fixtures.tests.dll +0 -0
- data/lib/net-1.1/nunit.framework.dll +0 -0
- data/lib/net-1.1/nunit.framework.extensions.dll +0 -0
- data/lib/net-1.1/nunit.framework.tests.dll +0 -0
- data/lib/net-1.1/nunit.framework.xml +5622 -0
- data/lib/net-1.1/nunit.mocks.dll +0 -0
- data/lib/net-1.1/nunit.mocks.tests.dll +0 -0
- data/lib/net-1.1/nunit.uikit.dll +0 -0
- data/lib/net-1.1/nunit.uikit.tests.dll +0 -0
- data/lib/net-1.1/nunit.util.dll +0 -0
- data/lib/net-1.1/nunit.util.tests.dll +0 -0
- data/lib/net-1.1/runFile.exe +0 -0
- data/lib/net-1.1/runFile.exe.config +43 -0
- data/lib/net-1.1/test-assembly.dll +0 -0
- data/lib/net-1.1/test-utilities.dll +0 -0
- data/lib/net-1.1/timing-tests.dll +0 -0
- data/lib/net-2.0/Failure.jpg +0 -0
- data/lib/net-2.0/Ignored.jpg +0 -0
- data/lib/net-2.0/NUnitFitTests.html +277 -0
- data/lib/net-2.0/NUnitTests.config +84 -0
- data/lib/net-2.0/NUnitTests.nunit +14 -0
- data/lib/net-2.0/Success.jpg +0 -0
- data/lib/net-2.0/clr.bat +96 -0
- data/lib/net-2.0/fit.dll +0 -0
- data/lib/net-2.0/loadtest-assembly.dll +0 -0
- data/lib/net-2.0/mock-assembly.dll +0 -0
- data/lib/net-2.0/nonamespace-assembly.dll +0 -0
- data/lib/net-2.0/notestfixtures-assembly.dll +0 -0
- data/lib/net-2.0/nunit-console-runner.dll +0 -0
- data/lib/net-2.0/nunit-console-x86.exe +0 -0
- data/lib/net-2.0/nunit-console-x86.exe.config +117 -0
- data/lib/net-2.0/nunit-console.exe +0 -0
- data/lib/net-2.0/nunit-console.exe.config +117 -0
- data/lib/net-2.0/nunit-console.tests.dll +0 -0
- data/lib/net-2.0/nunit-gui-runner.dll +0 -0
- data/lib/net-2.0/nunit-gui.tests.dll +0 -0
- data/lib/net-2.0/nunit-x86.exe +0 -0
- data/lib/net-2.0/nunit-x86.exe.config +121 -0
- data/lib/net-2.0/nunit.core.dll +0 -0
- data/lib/net-2.0/nunit.core.extensions.dll +0 -0
- data/lib/net-2.0/nunit.core.interfaces.dll +0 -0
- data/lib/net-2.0/nunit.core.tests.dll +0 -0
- data/lib/net-2.0/nunit.exe +0 -0
- data/lib/net-2.0/nunit.exe.config +121 -0
- data/lib/net-2.0/nunit.extensions.tests.dll +0 -0
- data/lib/net-2.0/nunit.fixtures.dll +0 -0
- data/lib/net-2.0/nunit.fixtures.tests.dll +0 -0
- data/lib/net-2.0/nunit.framework.dll +0 -0
- data/lib/net-2.0/nunit.framework.extensions.dll +0 -0
- data/lib/net-2.0/nunit.framework.tests.dll +0 -0
- data/lib/net-2.0/nunit.framework.xml +5622 -0
- data/lib/net-2.0/nunit.mocks.dll +0 -0
- data/lib/net-2.0/nunit.mocks.tests.dll +0 -0
- data/lib/net-2.0/nunit.uikit.dll +0 -0
- data/lib/net-2.0/nunit.uikit.tests.dll +0 -0
- data/lib/net-2.0/nunit.util.dll +0 -0
- data/lib/net-2.0/nunit.util.tests.dll +0 -0
- data/lib/net-2.0/runFile.exe +0 -0
- data/lib/net-2.0/runFile.exe.config +43 -0
- data/lib/net-2.0/test-assembly.dll +0 -0
- data/lib/net-2.0/test-utilities.dll +0 -0
- data/lib/net-2.0/timing-tests.dll +0 -0
- metadata +262 -0
data/docs/vsSupport.html
ADDED
|
@@ -0,0 +1,140 @@
|
|
|
1
|
+
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
|
2
|
+
<html>
|
|
3
|
+
<!-- Standard Head Part -->
|
|
4
|
+
<head>
|
|
5
|
+
<title>NUnit - VsSupport</title>
|
|
6
|
+
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
|
|
7
|
+
<meta http-equiv="Content-Language" content="en-US">
|
|
8
|
+
<link rel="stylesheet" type="text/css" href="nunit.css">
|
|
9
|
+
<link rel="shortcut icon" href="favicon.ico">
|
|
10
|
+
</head>
|
|
11
|
+
<!-- End Standard Head Part -->
|
|
12
|
+
|
|
13
|
+
<body>
|
|
14
|
+
|
|
15
|
+
<!-- Standard Header for NUnit.org -->
|
|
16
|
+
<div id="header">
|
|
17
|
+
<a id="logo" href="http://www.nunit.org"><img src="img/logo.gif" alt="NUnit.org" title="NUnit.org"></a>
|
|
18
|
+
<div id="nav">
|
|
19
|
+
<a href="http://www.nunit.org">NUnit</a>
|
|
20
|
+
<a class="active" href="index.html">Documentation</a>
|
|
21
|
+
</div>
|
|
22
|
+
</div>
|
|
23
|
+
<!-- End of Header -->
|
|
24
|
+
|
|
25
|
+
<div id="content">
|
|
26
|
+
|
|
27
|
+
<h2>Visual Studio Support</h2>
|
|
28
|
+
|
|
29
|
+
<p>Visual Studio support in this release is a sort of �poor man�s integration.� We have implemented
|
|
30
|
+
a number of features while avoiding any that would require using an Addin or otherwise
|
|
31
|
+
interacting with the Visual Studio extensibility model.</p>
|
|
32
|
+
|
|
33
|
+
<h3>Running From Within Visual Studio</h3>
|
|
34
|
+
|
|
35
|
+
<p>The most convenient way to do this is to set up a custom tool entry specifying the path to
|
|
36
|
+
NUnit as the command. For a VS2003 C# project, you can use $(TargetPath) for the arguments and
|
|
37
|
+
$(TargetDir) for the initial directory.
|
|
38
|
+
|
|
39
|
+
<p>With Visual Studio VS2005 this becomes a bit harder, because that release changed the
|
|
40
|
+
meaning of the 'Target' macros so they now point to the intermediate 'obj' directories rather
|
|
41
|
+
than the final output in one of the 'bin' directories. Here are some alternatives that
|
|
42
|
+
work in both versions:
|
|
43
|
+
|
|
44
|
+
<ul>
|
|
45
|
+
<li><b>$(ProjectDir)$(ProjectFileName)</b> to open the VS Project rather than the assembly.
|
|
46
|
+
If you use this approach, be sure to rename your config file accordingly and put it
|
|
47
|
+
in the same directory as the VS project file.
|
|
48
|
+
<li><b>$(ProjectDir)bin/Debug/$(TargetName)$(TargetExt)</b> to run the assembly directly.
|
|
49
|
+
Note that this requires hard-coding part of the path, including the configuration.
|
|
50
|
+
</ul>
|
|
51
|
+
|
|
52
|
+
<p>If you would like to debug your tests, use the Visual Studio
|
|
53
|
+
Debug | Processes� menu item to attach to NUnit after starting it and set breakpoints in
|
|
54
|
+
your test code as desired before running the tests.</p>
|
|
55
|
+
|
|
56
|
+
<h3>Using Console Interface to Debug Applications</h3>
|
|
57
|
+
|
|
58
|
+
<p>When the nunit-console program is run in debug mode under Visual Studio, it detects that it is
|
|
59
|
+
running in this mode and sends output to the Visual Studio output window. Output is formatted so
|
|
60
|
+
that double clicking any error or failure entries opens the appropriate test file at the location
|
|
61
|
+
where the failure was detected.</p>
|
|
62
|
+
|
|
63
|
+
<h3>Opening Visual Studio Projects</h3>
|
|
64
|
+
|
|
65
|
+
<p>When Visual Studio support is enabled, the File Open dialog displays the following supported
|
|
66
|
+
Visual Studio project types: C#, VB.Net, J# and C++. The project file is read and the
|
|
67
|
+
configurations and output assembly locations are identified. Since the project files do not contain
|
|
68
|
+
information about the most recently opened configuration, the output assembly for the first
|
|
69
|
+
configuration found (usually Debug) is loaded in the GUI. The tree shows the project as the toplevel
|
|
70
|
+
node with the assembly shown as its descendant.</p>
|
|
71
|
+
|
|
72
|
+
<p>Beginning with NUnit 2.2.2, you may also open a Visual Studio project by dragging it to the gui tree control.</p>
|
|
73
|
+
|
|
74
|
+
<p>When tests are run for a Visual studio project, they run just as if the output assembly had been
|
|
75
|
+
loaded with one exception. The default location for the config file is the directory containing the
|
|
76
|
+
project file and it�s default name is the same as the project file with an extension of .config.
|
|
77
|
+
For example, the following command would load the tests in the nunit.tests assembly using the
|
|
78
|
+
configuration file nunit.tests.dll.config located in the same directory as the dll.
|
|
79
|
+
<pre class="programtext"> nunit.exe nunit.tests.dll</pre>
|
|
80
|
+
On the other hand, the following command would load the tests using the configuration file
|
|
81
|
+
nunit.tests.config located in the same directory as the csproj file.
|
|
82
|
+
<pre class="programtext"> nunit.exe nunit.tests.csproj</pre>
|
|
83
|
+
The same consideration applies to running tests using the console runner.</p>
|
|
84
|
+
|
|
85
|
+
<h3>Opening Visual Studio Solutions</h3>
|
|
86
|
+
|
|
87
|
+
<p>When Visual Studio support is enabled, solution files may be opened as well. All the output
|
|
88
|
+
assemblies from contained projects of the types supported will be loaded in the tree. In the case
|
|
89
|
+
where all contained projects are located in the subdirectories beneath the solution, it will be
|
|
90
|
+
possible to load and run tests using this method directly.</p>
|
|
91
|
+
|
|
92
|
+
<p>Beginning with NUnit 2.2.2, you may also open a Visual Studio solution by dragging it to the gui tree control.</p>
|
|
93
|
+
|
|
94
|
+
<p>When a solution contains projects located elsewhere in the file system, it may not be possible to
|
|
95
|
+
run the tests � although the solution will generally load without problem. In this case, the Project
|
|
96
|
+
Editor should be use to modify and save the NUnit test project so that there is all referenced
|
|
97
|
+
assemblies are located in or beneath the application base directory.</p>
|
|
98
|
+
|
|
99
|
+
<h3>Adding Visual Studio Projects to the Open Test Project</h3>
|
|
100
|
+
|
|
101
|
+
<p>When Visual Studio support is enabled, the Project menu contains an active entry to add a VS
|
|
102
|
+
project to the loaded project. The output assembly will be added for each of the configurations
|
|
103
|
+
specified in the VS project.</p>
|
|
104
|
+
|
|
105
|
+
</div>
|
|
106
|
+
|
|
107
|
+
<!-- Submenu -->
|
|
108
|
+
<div id="subnav">
|
|
109
|
+
<ul>
|
|
110
|
+
<li><a href="index.html">NUnit 2.4.8</a></li>
|
|
111
|
+
<ul>
|
|
112
|
+
<li><a href="getStarted.html">Getting Started</a></li>
|
|
113
|
+
<li><a href="assertions.html">Assertions</a></li>
|
|
114
|
+
<li><a href="attributes.html">Attributes</a></li>
|
|
115
|
+
<li><a href="nunit-console.html">Console Runner</a></li>
|
|
116
|
+
<li><a href="nunit-gui.html">Gui Runner</a></li>
|
|
117
|
+
<li><a href="features.html">Other Features</a></li>
|
|
118
|
+
<ul>
|
|
119
|
+
<li><a href="configFiles.html">Configuration Files</a></li>
|
|
120
|
+
<li><a href="multiAssembly.html">Multiple Assemblies</a></li>
|
|
121
|
+
<li id="current"><a href="vsSupport.html">Visual Studio Support</a></li>
|
|
122
|
+
<li><a href="extensibility.html">Extensibility</a></li>
|
|
123
|
+
</ul>
|
|
124
|
+
<li><a href="releaseNotes.html">Release Notes</a></li>
|
|
125
|
+
<li><a href="samples.html">Samples</a></li>
|
|
126
|
+
<li><a href="license.html">License</a></li>
|
|
127
|
+
</ul>
|
|
128
|
+
</ul>
|
|
129
|
+
</div>
|
|
130
|
+
<!-- End of Submenu -->
|
|
131
|
+
|
|
132
|
+
|
|
133
|
+
<!-- Standard Footer for NUnit.org -->
|
|
134
|
+
<div id="footer">
|
|
135
|
+
Copyright © 2008 Charlie Poole. All Rights Reserved.
|
|
136
|
+
</div>
|
|
137
|
+
<!-- End of Footer -->
|
|
138
|
+
|
|
139
|
+
</body>
|
|
140
|
+
</html>
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,277 @@
|
|
|
1
|
+
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
2
|
+
<html>
|
|
3
|
+
<body>
|
|
4
|
+
<h1>NUnit Acceptance Tests</h1>
|
|
5
|
+
<p>
|
|
6
|
+
Developers love self-referential programs! Hence, NUnit has always run all it's
|
|
7
|
+
own tests, even those that are not really unit tests.
|
|
8
|
+
<p>Now, beginning with NUnit 2.4, NUnit has top-level tests using Ward Cunningham's
|
|
9
|
+
FIT framework. At this time, the tests are pretty rudimentary, but it's a start
|
|
10
|
+
and it's a framework for doing more.
|
|
11
|
+
<h2>Running the Tests</h2>
|
|
12
|
+
<p>Open a console or shell window and navigate to the NUnit bin directory, which
|
|
13
|
+
contains this file. To run the test under Microsoft .Net, enter the command
|
|
14
|
+
<pre> runFile NUnitFitTests.html TestResults.html .</pre>
|
|
15
|
+
To run it under Mono, enter
|
|
16
|
+
<pre> mono runFile.exe NUnitFitTests.html TestResults.html .</pre>
|
|
17
|
+
Note the space and dot at the end of each command. The results of your test
|
|
18
|
+
will be in TestResults.html in the same directory.
|
|
19
|
+
<h2>Platform and CLR Version</h2>
|
|
20
|
+
<table BORDER cellSpacing="0" cellPadding="5">
|
|
21
|
+
<tr>
|
|
22
|
+
<td colspan="2">NUnit.Fixtures.PlatformInfo</td>
|
|
23
|
+
</tr>
|
|
24
|
+
</table>
|
|
25
|
+
<h2>Verify Unit Tests</h2>
|
|
26
|
+
<p>
|
|
27
|
+
Load and run the NUnit unit tests, verifying that the results are as expected.
|
|
28
|
+
When these tests are run on different platforms, different numbers of tests may
|
|
29
|
+
be skipped, so the values for Skipped and Run tests are informational only.
|
|
30
|
+
<p>
|
|
31
|
+
The number of tests in each assembly should be constant across all platforms -
|
|
32
|
+
any discrepancy usually means that one of the test source files was not
|
|
33
|
+
compiled on the platform. There should be no failures and no tests ignored.
|
|
34
|
+
<p><b>Note:</b>
|
|
35
|
+
At the moment, the nunit.extensions.tests assembly is failing because the
|
|
36
|
+
fixture doesn't initialize addins in the test domain.
|
|
37
|
+
<p>
|
|
38
|
+
<table BORDER cellSpacing="0" cellPadding="5">
|
|
39
|
+
<tr>
|
|
40
|
+
<td colspan="6">NUnit.Fixtures.AssemblyRunner</td>
|
|
41
|
+
</tr>
|
|
42
|
+
<tr>
|
|
43
|
+
<td>Assembly</td>
|
|
44
|
+
<td>Tests()</td>
|
|
45
|
+
<td>Run()</td>
|
|
46
|
+
<td>Skipped()</td>
|
|
47
|
+
<td>Ignored()</td>
|
|
48
|
+
<td>Failures()</td>
|
|
49
|
+
</tr>
|
|
50
|
+
<tr>
|
|
51
|
+
<td>nunit.framework.tests.dll</td>
|
|
52
|
+
<td>397</td>
|
|
53
|
+
<td> </td>
|
|
54
|
+
<td> </td>
|
|
55
|
+
<td>0</td>
|
|
56
|
+
<td>0</td>
|
|
57
|
+
</tr>
|
|
58
|
+
<tr>
|
|
59
|
+
<td>nunit.core.tests.dll</td>
|
|
60
|
+
<td>355</td>
|
|
61
|
+
<td> </td>
|
|
62
|
+
<td> </td>
|
|
63
|
+
<td>0</td>
|
|
64
|
+
<td>0</td>
|
|
65
|
+
</tr>
|
|
66
|
+
<tr>
|
|
67
|
+
<td>nunit.util.tests.dll</td>
|
|
68
|
+
<td>238</td>
|
|
69
|
+
<td> </td>
|
|
70
|
+
<td> </td>
|
|
71
|
+
<td>0</td>
|
|
72
|
+
<td>0</td>
|
|
73
|
+
</tr>
|
|
74
|
+
<tr>
|
|
75
|
+
<td>nunit.mocks.tests.dll</td>
|
|
76
|
+
<td>43</td>
|
|
77
|
+
<td> </td>
|
|
78
|
+
<td> </td>
|
|
79
|
+
<td>0</td>
|
|
80
|
+
<td>0</td>
|
|
81
|
+
</tr>
|
|
82
|
+
<tr>
|
|
83
|
+
<td>nunit.extensions.tests.dll</td>
|
|
84
|
+
<td>5</td>
|
|
85
|
+
<td> </td>
|
|
86
|
+
<td> </td>
|
|
87
|
+
<td>0</td>
|
|
88
|
+
<td>0</td>
|
|
89
|
+
</tr>
|
|
90
|
+
<tr>
|
|
91
|
+
<td>nunit-console.tests.dll</td>
|
|
92
|
+
<td>40</td>
|
|
93
|
+
<td> </td>
|
|
94
|
+
<td> </td>
|
|
95
|
+
<td>0</td>
|
|
96
|
+
<td>0</td>
|
|
97
|
+
</tr>
|
|
98
|
+
<tr>
|
|
99
|
+
<td>nunit.uikit.tests.dll</td>
|
|
100
|
+
<td>34</td>
|
|
101
|
+
<td> </td>
|
|
102
|
+
<td> </td>
|
|
103
|
+
<td>0</td>
|
|
104
|
+
<td>0</td>
|
|
105
|
+
</tr>
|
|
106
|
+
<tr>
|
|
107
|
+
<td>nunit-gui.tests.dll</td>
|
|
108
|
+
<td>15</td>
|
|
109
|
+
<td> </td>
|
|
110
|
+
<td> </td>
|
|
111
|
+
<td>0</td>
|
|
112
|
+
<td>0</td>
|
|
113
|
+
</tr>
|
|
114
|
+
<tr>
|
|
115
|
+
<td>nunit.fixtures.tests.dll</td>
|
|
116
|
+
<td>6</td>
|
|
117
|
+
<td> </td>
|
|
118
|
+
<td> </td>
|
|
119
|
+
<td>0</td>
|
|
120
|
+
<td>0</td>
|
|
121
|
+
</tr>
|
|
122
|
+
</table>
|
|
123
|
+
<h2>Code Snippet Tests</h2>
|
|
124
|
+
<p>
|
|
125
|
+
These tests create a test assembly from a snippet of code and then load and run
|
|
126
|
+
the tests that it contains, verifying that the structure of the loaded tests is
|
|
127
|
+
as expected and that the number of tests run, skipped, ignored or failed is
|
|
128
|
+
correct.
|
|
129
|
+
<p>
|
|
130
|
+
<table BORDER cellSpacing="0" cellPadding="5">
|
|
131
|
+
<tr>
|
|
132
|
+
<td colspan="6">NUnit.Fixtures.SnippetRunner</td>
|
|
133
|
+
</tr>
|
|
134
|
+
<tr>
|
|
135
|
+
<td>Code</td>
|
|
136
|
+
<td>Tree()</td>
|
|
137
|
+
<td>Run()</td>
|
|
138
|
+
<td>Skipped()</td>
|
|
139
|
+
<td>Ignored()</td>
|
|
140
|
+
<td>Failures()</td>
|
|
141
|
+
</tr>
|
|
142
|
+
<tr>
|
|
143
|
+
<td><pre>public class TestClass
|
|
144
|
+
{
|
|
145
|
+
}</pre>
|
|
146
|
+
</td>
|
|
147
|
+
<td>EMPTY</td>
|
|
148
|
+
<td>0</td>
|
|
149
|
+
<td>0</td>
|
|
150
|
+
<td>0</td>
|
|
151
|
+
<td>0</td>
|
|
152
|
+
</tr>
|
|
153
|
+
<tr>
|
|
154
|
+
<td><pre>using NUnit.Framework;
|
|
155
|
+
|
|
156
|
+
[TestFixture]
|
|
157
|
+
public class TestClass
|
|
158
|
+
{
|
|
159
|
+
}</pre>
|
|
160
|
+
</td>
|
|
161
|
+
<td>TestClass</td>
|
|
162
|
+
<td>0</td>
|
|
163
|
+
<td>0</td>
|
|
164
|
+
<td>0</td>
|
|
165
|
+
<td>0</td>
|
|
166
|
+
</tr>
|
|
167
|
+
<tr>
|
|
168
|
+
<td><pre>using NUnit.Framework;
|
|
169
|
+
|
|
170
|
+
[TestFixture]
|
|
171
|
+
public class TestClass
|
|
172
|
+
{
|
|
173
|
+
[Test]
|
|
174
|
+
public void T1() { }
|
|
175
|
+
[Test]
|
|
176
|
+
public void T2() { }
|
|
177
|
+
[Test]
|
|
178
|
+
public void T3() { }
|
|
179
|
+
}</pre>
|
|
180
|
+
</td>
|
|
181
|
+
<td><pre>TestClass
|
|
182
|
+
>T1
|
|
183
|
+
>T2
|
|
184
|
+
>T3</pre>
|
|
185
|
+
</td>
|
|
186
|
+
<td>3</td>
|
|
187
|
+
<td>0</td>
|
|
188
|
+
<td>0</td>
|
|
189
|
+
<td>0</td>
|
|
190
|
+
</tr>
|
|
191
|
+
<tr>
|
|
192
|
+
<td><pre>using NUnit.Framework;
|
|
193
|
+
|
|
194
|
+
[TestFixture]
|
|
195
|
+
public class TestClass1
|
|
196
|
+
{
|
|
197
|
+
[Test]
|
|
198
|
+
public void T1() { }
|
|
199
|
+
}
|
|
200
|
+
|
|
201
|
+
[TestFixture]
|
|
202
|
+
public class TestClass2
|
|
203
|
+
{
|
|
204
|
+
[Test]
|
|
205
|
+
public void T2() { }
|
|
206
|
+
[Test]
|
|
207
|
+
public void T3() { }
|
|
208
|
+
}</pre>
|
|
209
|
+
</td>
|
|
210
|
+
<td><pre>TestClass1
|
|
211
|
+
>T1
|
|
212
|
+
TestClass2
|
|
213
|
+
>T2
|
|
214
|
+
>T3</pre>
|
|
215
|
+
</td>
|
|
216
|
+
<td>3</td>
|
|
217
|
+
<td>0</td>
|
|
218
|
+
<td>0</td>
|
|
219
|
+
<td>0</td>
|
|
220
|
+
</tr>
|
|
221
|
+
<tr>
|
|
222
|
+
<td><pre>using NUnit.Framework;
|
|
223
|
+
|
|
224
|
+
[TestFixture]
|
|
225
|
+
public class TestClass
|
|
226
|
+
{
|
|
227
|
+
[Test]
|
|
228
|
+
public void T1() { }
|
|
229
|
+
[Test, Ignore]
|
|
230
|
+
public void T2() { }
|
|
231
|
+
[Test]
|
|
232
|
+
public void T3() { }
|
|
233
|
+
}</pre>
|
|
234
|
+
</td>
|
|
235
|
+
<td><pre>TestClass
|
|
236
|
+
>T1
|
|
237
|
+
>T2
|
|
238
|
+
>T3</pre>
|
|
239
|
+
</td>
|
|
240
|
+
<td>2</td>
|
|
241
|
+
<td>0</td>
|
|
242
|
+
<td>1</td>
|
|
243
|
+
<td>0</td>
|
|
244
|
+
</tr>
|
|
245
|
+
<tr>
|
|
246
|
+
<td><pre>using NUnit.Framework;
|
|
247
|
+
|
|
248
|
+
[TestFixture]
|
|
249
|
+
public class TestClass
|
|
250
|
+
{
|
|
251
|
+
[Test]
|
|
252
|
+
public void T1() { }
|
|
253
|
+
[Test, Explicit]
|
|
254
|
+
public void T2() { }
|
|
255
|
+
[Test]
|
|
256
|
+
public void T3() { }
|
|
257
|
+
}</pre>
|
|
258
|
+
</td>
|
|
259
|
+
<td><pre>TestClass
|
|
260
|
+
>T1
|
|
261
|
+
>T2
|
|
262
|
+
>T3</pre>
|
|
263
|
+
</td>
|
|
264
|
+
<td>2</td>
|
|
265
|
+
<td>1</td>
|
|
266
|
+
<td>0</td>
|
|
267
|
+
<td>0</td>
|
|
268
|
+
</tr>
|
|
269
|
+
</table>
|
|
270
|
+
<h2>Summary Information</h2>
|
|
271
|
+
<table BORDER cellSpacing="0" cellPadding="5">
|
|
272
|
+
<tr>
|
|
273
|
+
<td colspan="2">fit.Summary</td>
|
|
274
|
+
</tr>
|
|
275
|
+
</table>
|
|
276
|
+
</body>
|
|
277
|
+
</html>
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="utf-8" ?>
|
|
2
|
+
<configuration>
|
|
3
|
+
<!--
|
|
4
|
+
This is the configuration file for the NUnitTests.nunit test project. You may
|
|
5
|
+
need to create a similar configuration file for your own test project.
|
|
6
|
+
-->
|
|
7
|
+
|
|
8
|
+
<!--
|
|
9
|
+
The <NUnit> section is only needed if you want to use a non-default value
|
|
10
|
+
for any of the settings. It is commented out below. If you are going to use
|
|
11
|
+
it, you must deifne the NUnit section group and the sections you need.
|
|
12
|
+
|
|
13
|
+
The syntax shown here works for most runtimes. If NUnit fails at startup, you
|
|
14
|
+
can try specifying the name of the assembly containing the NameValueSectionHandler:
|
|
15
|
+
|
|
16
|
+
<section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler, System" />
|
|
17
|
+
|
|
18
|
+
If that fails, try the fully qualified name of the assembly:
|
|
19
|
+
|
|
20
|
+
<section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler, System,
|
|
21
|
+
Version=2.0.50727.832, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
|
|
22
|
+
|
|
23
|
+
Unfortunately, this last approach makes your config file non-portable across runtimes.
|
|
24
|
+
-->
|
|
25
|
+
|
|
26
|
+
<!--
|
|
27
|
+
<configSections>
|
|
28
|
+
<sectionGroup name="NUnit">
|
|
29
|
+
<section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler"/>
|
|
30
|
+
<section name="TestRunner" type="System.Configuration.NameValueSectionHandler"/>
|
|
31
|
+
</sectionGroup>
|
|
32
|
+
</configSections>
|
|
33
|
+
-->
|
|
34
|
+
|
|
35
|
+
<appSettings>
|
|
36
|
+
<!-- User application and configured property settings go here.-->
|
|
37
|
+
<!-- Example: <add key="settingName" value="settingValue"/> -->
|
|
38
|
+
<add key="test.setting" value="54321" />
|
|
39
|
+
</appSettings>
|
|
40
|
+
|
|
41
|
+
<!-- Sample NUnit section group showing all default values -->
|
|
42
|
+
<!--
|
|
43
|
+
<NUnit>
|
|
44
|
+
<TestCaseBuilder>
|
|
45
|
+
<add key="OldStyleTestCases" value="false" />
|
|
46
|
+
</TestCaseBuilder>
|
|
47
|
+
<TestRunner>
|
|
48
|
+
<add key="ApartmentState" value="MTA" />
|
|
49
|
+
<add key="ThreadPriority" value="Normal" />
|
|
50
|
+
<add key="DefaultLogThreshold" value="Error" />
|
|
51
|
+
</TestRunner>
|
|
52
|
+
</NUnit>
|
|
53
|
+
-->
|
|
54
|
+
<!--
|
|
55
|
+
The following <runtime> section allows running nunit tests under
|
|
56
|
+
.NET 1.0 by redirecting assemblies. The appliesTo attribute
|
|
57
|
+
causes the section to be ignored except under .NET 1.0.
|
|
58
|
+
-->
|
|
59
|
+
<runtime>
|
|
60
|
+
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"
|
|
61
|
+
appliesTo="v1.0.3705">
|
|
62
|
+
<dependentAssembly>
|
|
63
|
+
<assemblyIdentity name="System" publicKeyToken="b77a5c561934e089" culture="" />
|
|
64
|
+
<bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
|
|
65
|
+
</dependentAssembly>
|
|
66
|
+
<dependentAssembly>
|
|
67
|
+
<assemblyIdentity name="System.Data" publicKeyToken="b77a5c561934e089" culture="" />
|
|
68
|
+
<bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
|
|
69
|
+
</dependentAssembly>
|
|
70
|
+
<dependentAssembly>
|
|
71
|
+
<assemblyIdentity name="System.Drawing" publicKeyToken="b03f5f7f11d50a3a" culture="" />
|
|
72
|
+
<bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
|
|
73
|
+
</dependentAssembly>
|
|
74
|
+
<dependentAssembly>
|
|
75
|
+
<assemblyIdentity name="System.Windows.Forms" publicKeyToken="b77a5c561934e089" culture="" />
|
|
76
|
+
<bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
|
|
77
|
+
</dependentAssembly>
|
|
78
|
+
<dependentAssembly>
|
|
79
|
+
<assemblyIdentity name="System.Xml" publicKeyToken="b77a5c561934e089" culture="" />
|
|
80
|
+
<bindingRedirect oldVersion="1.0.5000.0" newVersion="1.0.3300.0" />
|
|
81
|
+
</dependentAssembly>
|
|
82
|
+
</assemblyBinding>
|
|
83
|
+
</runtime>
|
|
84
|
+
</configuration>
|