source: BMXNET_RPMS_dotNET_UTILITIES-BMX/branch/IHS BMX Framework/lib/NUnit/NUnit-2.5.10.11092/doc/settingsDialog.html@ 1146

Last change on this file since 1146 was 1146, checked in by Sam Habiel, 13 years ago

Initial Import of BMX4

File size: 12.0 KB
Line 
1<!-- saved from url=(0014)about:internet --><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
2<html>
3<!-- Standard Head Part -->
4<head>
5<title>NUnit - SettingsDialog</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>Settings Dialog</h2>
28
29<p>The Settings Dialog is displayed using the Tools | Settings menu item and allows the user to
30control some aspects of NUnit’s operation. Beginning with NUnit 2.4.4, a tree-based dialog
31replaced the older tabbed format.</p>
32
33<hr><h3>Gui Settings - General</h3><hr>
34
35<div class="screenshot-right">
36 <img src="img/generalSettings.jpg"></div>
37
38<h3>Gui Display</h3>
39
40<h4>Full Gui</h4>
41<p>Displays the complete gui - as in prior versions of NUnit. This includes the
42 test result tabs and the progress bar.</p>
43
44<h4>Mini Gui</h4>
45<p>Switches the display to the mini-gui, which consists of the tree display
46 only.</p>
47<h3>Recent Files</h3>
48
49<p>The <b>Display ... files in list</b> TextBox allows the user to choose the number
50of entries to display in the recent files list.
51
52<p>Normally, NUnit checks that project files still exist before
53displaying them in the recent files list. This can cause long delays if the
54file is on a network connection that is no longer available. Unchecking
55<b>Check that files exist before listing</b> will avoid this delay, so
56long as the missing file is not actually selected.
57
58<p>If <b>Load most recent project at startup</b> is checked, the GUI will load the
59last file opened unless it is run with a specific filename or with the
60<code>/noload</code> parameter.</p>
61
62<hr style="clear: both"><h3>Gui Settings - Tree Display</h3><hr>
63
64<div class="screenshot-right">
65 <img src="img/treeDisplaySettings.jpg"></div>
66
67<h3>Tree View</h3>
68
69<p>The list box allows selecting the degree of expansion of the tree when tests are loaded:</p>
70<blockquote>
71<p><b>Auto</b> – selects a setting based on the space available for the tree display.</p>
72<p><b>Expand</b> – expands all tests</p>
73<p><b>Collapse</b> – collapses all tests</p>
74<p><b>Hide Tests</b> – expands all suites except for the fixtures themselves.</p>
75</blockquote>
76
77<p>If <b>Clear results when reloading</b> is checked, an automatic or manual reload will reinitialize all
78test nodes in the tree (grey display) – if it is not checked, result information for tests that do
79not seem to have changed will be retained.</p>
80
81<p>If <b>Save visual state of each project</b> is checked, NUnit saves the state of the tree
82and restores it when the project is next opened. The information saved includes which
83branches of the tree are expanded, the selected node, any checked nodes and any
84category selection.
85
86<p>If <b>Show Checkboxes</b> is checked, the tree includes checkboxes, which may
87 be used to select multiple tests for running. This setting is also available
88 in the <b>View | Tree</b> menu.</p>
89
90<h3>Test Structure</h3>
91
92<p>If <b>Automatic Namespace suites</b> is selected, tests will be
93 shown in a hierarchical listing based on namespaces. This is the
94 standard display as used in versions prior to NUnit 2.4.
95
96<p>If <b>Flat list of TestFixtures</b> is selected, tests will be
97 shown as a sequential list of fixtures.
98
99<hr style="clear: both"><h3>Gui Settings - Test Results</h3><hr>
100
101<div class="screenshot-right">
102 <img src="img/testResultSettings.jpg"></div>
103
104<h3>Errors Tab</h3>
105
106<p>Check <b>Display Errors and Failures Tab</b> to display the
107<b>Errors and Failures</b> tab, which shows information about failing tests.
108
109<p>Check <b>Enable Failure ToolTips</b> to display the tip window over the
110Errors and Failures display and the stack trace. Clear it if you prefer not
111to see the tip window.</p>
112
113<p>Check <b>Enable Word Wrap</b> to turn on word wrapping
114in the Errors and Failures display. While you can select this item and the
115preceding one at the same time, they do not interact well, so you will
116normally choose one or the other.</p>
117
118<h3>Not Run Tab</h3>
119
120<p>Check <b>Display Tests Not Run Tab</b> to display the
121<b>Tests Not Run</b> tab, which shows information about tests that were
122skipped or ignored.
123
124<hr style="clear: both"><h3>Gui Settings - Text Output</h3><hr>
125
126<div class="screenshot-right">
127 <img src="img/textOutputSettings.jpg"></div>
128
129<h3>Select Tab</h3>
130
131<p>The <b>Select Tab</b> dropdown list is used to select one of the output tabs, for which
132settings are to be viewed or changed. It also contains entries that allow
133you to add a new tab or edit the list of tabs.
134
135<p>The <b>Restore Defaults</b> button is used to restore the default
136setting, which is a single tab labeled "Text Output." The default tab
137displays all types of output and includes a label for each test that
138displays text.
139
140<p>The <b>Title</b> text box is used to modify the title displayed
141for the selected output tab.
142
143<p><b>Enabled</b> is checked by default. If you uncheck it,
144the selected tab will be removed from the tab control. This allows you to temporarily
145suppress output to a tab without actually removing its definition.
146
147<h3>Content</h3>
148
149<p>The four check boxes enable or disable a particular type of output
150on the selected output window. For each type, the display captures
151output produced while your test is running - either by the test
152itself or by the program you are testing.
153
154<h4>Standard Output</h4>
155<p>Captures all output written to Console.Out.
156
157<h4>Error Output</h4>
158<p>Captures all output written to Console.Error.
159
160<h4>Trace Output</h4>
161<p>Captures all output written to Trace or Debug.
162
163<h4>Log Output</h4>
164<p>Captures output written to a log4net log. NUnit captures
165all output at the Error level or above unless another level
166is specified for the DefaultLogThreshold setting in the
167configuration file for the test assembly or project.
168
169<h3>Test Labels</h3>
170
171<p>Check <b>Display TestCase Labels</b> to precede text in the output window
172with the name of the test that produced it.</p>
173
174<p>Check <b>Suppress label if no output is displayed</b> to eliminate display
175of labels for tests that produce no output in the window.
176
177
178<hr style="clear: both"><h3>Test Loader Settings - Assembly Isolation</h3><hr>
179
180<div class="screenshot-right">
181 <img src="img/testLoadSettings.jpg"></div>
182
183<h3>Default Process Model</h3>
184
185<p>These settings determine NUnit's default use of operating system
186processes and may be overridden by settings in the NUnit project.
187
188<p>If <b>Run tests directly in the NUnit process</b> is selected,
189all tests are run in a test domain in the same process as NUnit.
190This is the way previous versions of NUnit ran tests and is the
191default setting.
192
193<p>If <b>Run tests in a single separate process</b> is selected,
194a separate process is used for all tests.
195
196<p>If <b>Run tests in a separate process per Assembly </b> is selected,
197a separate process is used for each test assembly.
198
199<h3>Default Domain Usage</h3>
200
201<p>If <b>Use a separate AppDomain per Assembly</b> is selected, each assembly
202 in a multiple-assembly test run will be loaded in a separate AppDomain.
203 This setting is not available when <b>Run tests in a separate process
204 per Assembly</b> is selected above.
205
206<p>If <b>Use a single AppDomain for all tests</b> is selected, all assemblies in
207 a multiple-assembly test run will use the same AppDomain. This was
208 the standard behavior of NUnit prior to version 2.4 and is the
209 default setting.
210
211<p>If <b>Merge tests across assemblies</b> is checked, the display of tests
212 will not be divided across assemblies. If automatic namespace suites are
213 used, they will be merged across all assemblies. This option is only
214 available when tests are run in the same appdomain.
215
216<hr style="clear: both"><h3>Test Loader Settings - Assembly Reload</h3><hr>
217
218<div class="screenshot-right">
219 <img src="img/assemblyReloadSettings.jpg"></div>
220
221<h3>Assembly Reload</h3>
222
223<p>If <b>Reload before each test run</b> is checked, a reload will occur whenever the run button is
224pressed whether the assemblies appear to have changed or not.</p>
225
226<p>If <b>Reload when test assembly changes</b> is checked, assemblies are watched for any change and
227an automatic reload is initiated. This item is disabled on Windows 98 or ME.</p>
228
229<p>If <b>Re-run last tests run</b> is checked, tests are re-run whenever a Reload
230 takes place.</p>
231
232<hr style="clear: both"><h3>Test Loader Settings - Advanced</h3><hr>
233
234<div class="screenshot-right">
235 <img src="img/advancedSettings.jpg"></div>
236
237<h3>Shadow Copy</h3>
238
239<p>NUnit normally uses .Net shadow-copying in order to allow you to edit
240and recompile assemblies while it is running. Uncheck this box to disable
241shadow-copy only if you have a particular problem that requires it.</p>
242
243<p><b>Note:</b> If you are tempted to disable shadow copy in order to access
244files in the same directory as your assembly, you should be aware that there
245are alternatives. Consider using the Assembly.Codebase property rather than
246Assembly.Location.
247
248
249<hr style="clear: both"><h3>IDE Support Settings - Visual Studio</h3><hr>
250
251<div class="screenshot-right">
252 <img src="img/visualStudioSettings.jpg"></div>
253
254<h3>Visual Studio</h3>
255
256<p>If <b>Enable Visual Studio Support</b> is checked, the user will be able to open Visual Studio projects
257and solutions and add Visual Studio projects to existing test projects.</p>
258
259<hr style="clear: both"><h3>Advanced Settings - Internal Trace</h3><hr>
260
261<div class="screenshot-right">
262 <img src="img/internalTraceSettings.jpg"></div>
263
264<h3>Internal Trace</h3>
265
266<p>The <b>Trace Level</b> dropdown controls the level of internal trace output.</p>
267
268
269
270
271</div>
272
273<!-- Submenu -->
274<div id="subnav">
275<ul>
276<li><a href="index.html">NUnit 2.5.10</a></li>
277<ul>
278<li><a href="getStarted.html">Getting&nbsp;Started</a></li>
279<li><a href="assertions.html">Assertions</a></li>
280<li><a href="constraintModel.html">Constraints</a></li>
281<li><a href="attributes.html">Attributes</a></li>
282<li><a href="runningTests.html">Running&nbsp;Tests</a></li>
283<ul>
284<li><a href="nunit-console.html">Console&nbsp;Runner</a></li>
285<li><a href="nunit-gui.html">Gui&nbsp;Runner</a></li>
286<ul>
287<li><a href="guiCommandLine.html">Command-Line</a></li>
288<li><a href="mainMenu.html">Main&nbsp;Menu</a></li>
289<li><a href="contextMenu.html">Context&nbsp;Menu</a></li>
290<li id="current"><a href="settingsDialog.html">Settings&nbsp;Dialog</a></li>
291<li><a href="addinsDialog.html">Addins&nbsp;Dialog</a></li>
292<li><a href="testProperties.html">Test&nbsp;Properties</a></li>
293<li><a href="configEditor.html">Configuration&nbsp;Editor</a></li>
294<li><a href="projectEditor.html">Project&nbsp;Editor</a></li>
295</ul>
296<li><a href="pnunit.html">PNUnit&nbsp;Runner</a></li>
297<li><a href="nunit-agent.html">NUnit&nbsp;Agent</a></li>
298<li><a href="runtimeSelection.html">Runtime&nbsp;Selection</a></li>
299<li><a href="assemblyIsolation.html">Assembly&nbsp;Isolation</a></li>
300<li><a href="configFiles.html">Configuration&nbsp;Files</a></li>
301<li><a href="multiAssembly.html">Multiple&nbsp;Assemblies</a></li>
302<li><a href="vsSupport.html">Visual&nbsp;Studio&nbsp;Support</a></li>
303</ul>
304<li><a href="extensibility.html">Extensibility</a></li>
305<li><a href="releaseNotes.html">Release&nbsp;Notes</a></li>
306<li><a href="samples.html">Samples</a></li>
307<li><a href="license.html">License</a></li>
308</ul>
309</ul>
310</div>
311<!-- End of Submenu -->
312
313
314<!-- Standard Footer for NUnit.org -->
315<div id="footer">
316 Copyright &copy; 2010 Charlie Poole. All Rights Reserved.
317</div>
318<!-- End of Footer -->
319
320</body>
321</html>
Note: See TracBrowser for help on using the repository browser.