1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<!-- Standard Head Part -->
<head>
<title>NUnit - Nunit-gui</title>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta http-equiv="Content-Language" content="en-US">
<link rel="stylesheet" type="text/css" href="nunit.css">
<link rel="shortcut icon" href="favicon.ico">
</head>
<!-- End Standard Head Part -->
<body>
<!-- Standard Header for NUnit.org -->
<div id="header">
<a id="logo" href="http://www.nunit.org"><img src="img/logo.gif" alt="NUnit.org" title="NUnit.org"></a>
<div id="nav">
<a href="http://www.nunit.org">NUnit</a>
<a class="active" href="index.html">Documentation</a>
</div>
</div>
<!-- End of Header -->
<div id="content">
<h2>NUnit Gui Runner</h2>
<p>The nunit.exe program is a graphical runner. It shows the tests in an
explorer-like browser window and provides a visual indication of the success or
failure of the tests. It allows you to selectively run single tests or suites
and reloads automatically as you modify and re-compile your code. The following
is a screenshot of NUnit running the same mock-assembly.dll shown in the
previous example.</p>
<div class="screenshot-left">
<img src="img/gui-screenshot.jpg"></div>
<p>
<h4>Tree Display</h4>
<p>This version of NUnit uses symbols in the test tree, which allow those who
are unable to easily distinguish colors to determine the test status.
Successful tests are colored green, with a check mark. Tests that are ignored
are marked with a yellow circle, containing a question mark. If any
tests had failed, they would be marked red, with an X symbol.</p>
<p>In this example, there were a total of 11 test cases, but one of them was not
counted because it was marked Explicit. Note that it is shown as a gray
circle in the tree. Of the remaining 10 tests, 5 were run successfully and
5 were ignored.</p>
<p>The symbols shown in the tree are actually files in the NUnit bin directory.
These files are named Success.jpg, Failure.jpg and Ignored.jpg and may be
modified or replaced by the user.</p>
<h4>Progress Bar</h4>
<p>The progress bar shows the progress of the test. It is colored according
to the "worst" result obtained: red if there were any failures, yellow if
some tests were ignored and green for success.
<h4>Result Tabs</h4>
<p>The tabs along the bottom of the display show the results of running
a test. The <b>Errors and Failures</b> tab displays the error message
and stack trace for both unexpected exceptions and assertion failures.
The <b>Tests Not Run</b> tab provides a list of all tests that were
selected for running but were not run, together with the reason. The
remaining tabs display text output from the tests. In the image above,
there are four of them: <b>Console.Out</b>, <b>Console.Error</b>,
<b>Trace</b> and <b>Log</b>. This is the default display, but these
output tabs are actually under user control and may be removed or
modified or have new tabs added.
For more information, see the documentation for the
<a href="optionsDialog.html">Options Dialog</a>.
<h3>Mini-Gui</h3>
<p>With the release of NUnit 2.4, an alternate "mini-gui" is also available. It
may be selected from the View menu. The following screenshot shows the mini
gui displaying the NUnit tests.</p>
<div class="screenshot">
<img src="img/miniGui.jpg"></div>
<h3>NUnit on 64-Bit Platforms</h3>
<p>The .NET 2.0 version of nunit.exe is built using /platform:anycpu,
which causes it to be jit-compiled to 32-bit code on a 32-bit system and 64-bit code
on a 64 bit system. This causes an exception when NUnit is used to test a 32-bit
application on a 64-bit system. To avoid this problem, use nunit-x86.exe ,
which is built using /platform:x86, when testing 32-bit code on a
64-bit system.
</div>
<!-- Submenu -->
<div id="subnav">
<ul>
<li><a href="index.html">NUnit 2.4.7</a></li>
<ul>
<li><a href="getStarted.html">Getting Started</a></li>
<li><a href="assertions.html">Assertions</a></li>
<li><a href="attributes.html">Attributes</a></li>
<li><a href="nunit-console.html">Console Runner</a></li>
<li id="current"><a href="nunit-gui.html">Gui Runner</a></li>
<ul>
<li><a href="guiCommandLine.html">Command-Line</a></li>
<li><a href="mainMenu.html">Main Menu</a></li>
<li><a href="contextMenu.html">Context Menu</a></li>
<li><a href="optionsDialog.html">Options Dialog</a></li>
<li><a href="addinsDialog.html">Addins Dialog</a></li>
<li><a href="testProperties.html">Test Properties</a></li>
<li><a href="configEditor.html">Configuration Editor</a></li>
<li><a href="projectEditor.html">Project Editor</a></li>
</ul>
<li><a href="features.html">Other Features</a></li>
<li><a href="releaseNotes.html">Release Notes</a></li>
<li><a href="samples.html">Samples</a></li>
<li><a href="license.html">License</a></li>
</ul>
</ul>
</div>
<!-- End of Submenu -->
<!-- Standard Footer for NUnit.org -->
<div id="footer">
Copyright © 2008 Charlie Poole. All Rights Reserved.
</div>
<!-- End of Footer -->
</body>
</html>
|