/usr/share/doc/nunit/html/projectEditor.html is in libnunit-doc 2.6.0.12051+dfsg-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 | <!-- saved from url=(0014)about:internet --><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<!-- Standard Head Part -->
<head>
<title>NUnit - ProjectEditor</title>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta http-equiv="Content-Language" content="en-US">
<meta name="norton-safeweb-site-verification" content="tb6xj01p4hgo5x-8wscsmq633y11-e6nhk-bnb5d987bseanyp6p0uew-pec8j963qlzj32k5x9h3r2q7wh-vmy8bbhek5lnpp5w4p8hocouuq39e09jrkihdtaeknua" />
<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>Project Editor</h2>
<p>Beginning with NUnit 2.6, the Project Editor is a separate program, which may be executed
directly or run through the Project | Edit dropdown menu of the NUnit GUI. The editor now
provides two main views of the project: a property-oriented view based on the Project Editor
that was built into earlier versions of the NUnit GUI and an xml view, which allows direct
editing of the .nunit file.
<h2>Property View</h2>
<p>This view consists of a common area and two tabs, as seen in the image below.</p>
<div class="screenshot-left">
<img src="img/generalTab.jpg"></div>
<h3>Common Area</h3>
<p>The common area of the Project Editor contains information pertaining to
the project as a whole. Information that applies to a particular configuration
is displayed in the General and Assemblies tabs.
<h4>Project Path</h4>
<p>This label shows the full path to the project file. In the case of a
wrapper project, the path is set to the same directory as the assembly
that was initially opened.
<h4>Application Base</h4>
<p>This TextBox allows the user to change the project AppBase, which defaults to
the directory of the project file. The button to the right of the TextBox
allows the user to browse and select a directory.
<h4>Process Model</h4>
<p>This dropdown list allows you to specify how operating system processes are
used in loading and running the tests in this project. Four settings are
defined:
<ul>
<li>The <b>Default</b> setting refers to the option selected by the user
on the Assembly Isolation page of the NUnit Settings Dialog.
<li><b>Single</b> means that tests are run in a test domain in the
same process as NUnit. This is the way previous versions of NUnit
ran tests.
<li><b>Separate</b> means that all the tests are run in a separate process
that NUnit creates.
<li><b>Multiple</b> means that NUnit will create a separate process for
each test assembly in the project and run its tests there.
</ul>
<h4>Domain Usage</h4>
<p>This dropdown list allows you to specify how tests are loaded into
AppDomains by NUnit. Three settings are defined:
<ul>
<li>The <b>Default</b> setting refers to the option selected by the user
on the Assembly Isolation page of the NUnit Settings Dialog.
<li><b>Single</b> means that all tests will run in a single test domain
created by NUnit. This was the way versions of NUnit prior to 2.4
ran tests.
<li><b>Multiple</b> means that each test assembly is loaded into a
separate AppDomain. This setting is not available when Multiple
processes are selected in the Process Model dropown.
</ul>
<h4>Configuration</h4>
<p>This dropdown list allows you to select the particular configuration
within a project that is displayed in the bottom part of the dialog.
<h4>Edit Configs...</h4>
<p>This button opens the
<a href="configEditor.html">Configuration Editor</a>,
which allows you to add, delete or rename configs and set the
active configuration.
<h3>General Tab</h3>
<p>The General tab allows setting a number of options pertaining to the selected configuration, all of
which will be stored in the NUnit project file as attributes of the <config> xml node.</p>
<h4>Runtime</h4>
<p>This dropdown allows you to select a particular runtime framework to be used
for loading and running tests under the current configuration. Currently,
only Microsoft .NET and Mono are supported. If <b>Any</b> is selected, the
tests will be run under the same runtime that NUnit itself is currently using.
<h4>Version</h4>
<p>This ComboBox allows you to select the particular version of the runtime framework
to be used for loading and running tests under the current configuration. The
dropdown list contains entries for
<ul>
<li>Default
<li>1.0
<li>1.1
<li>2.0
<li>4.0
</ul>
<p>If you select "Default" the assemblies in the project are examined to determine
the version that is required.
See <a href="runtimeSelection.html">Runtime Selection</a> for
more information on how NUnit selects the version to be used.
<p>In special cases, you may wish to enter a version number that is not listed
in the list box. You may specify the version using two, three or four
components. The version you provide will be saved as you enter it. Leaving
the text box blank is equivalent to selecting "Default."
<p><b>Note:</b> Running tests under a different runtime or version from the one that NUnit
is currently using will force them to run in a separate process.
<p><b>Note:</b> To conform with normal usage, specifying Mono as the runtime
with "1.0" as the version results in use of the Mono 1.0 profile, equating
to version 1.1.4322.
<h4>ApplicationBase</h4>
<p>The ApplicationBase defaults to the directory containing the project file. Beginning
with NUnit 2.2.3, it may be set to any location that is desired.</p>
<h4>Configuration File Name</h4>
<p>The configuration file defaults to the name of the test project with the extension changed
from .nunit to .config. The user may substitute another name.</p>
<h4>PrivateBinPath</h4>
<p>By default, the PrivateBinPath is generated from the assembly locations specified on the
Assemblies Tab. For those applications requiring a different level of control, it may be
specified manually or using this editor or placed in the configuration file.</p>
<h3>Assemblies Tab</h3>
<p>The assemblies tab contains the list of assemblies that form part of this test project.</p>
<p>Note: Although the dialog shows the location of assemblies as absolute paths, they are always
persisted in the NUnit project file as paths relative to the application base. This allows moving
projects as a whole to a different directory location.</p>
<div class="screenshot-left">
<img src="img/assembliesTab.jpg"></div>
<h4>Add...</h4>
<p>Opens a dialog allowing adding an assembly to this configuration. If Visual
Stuio support is enabled, you may also select and add a VS project.</p>
<h4>Remove</h4>
<p>After confirmation, removes the selected assembly from this configuration.</p>
<h4>Assembly Path</h4>
<p>This text box displays the full path to the selected assembly. You may edit
the contents to change the path to the assembly.
<h2>XML View</h2>
<p>This view simply displays the XML from the project file, as seen here. You may
edit the XML directly.</p>
<div class="screenshot-left">
<img src="img/xmlView.jpg"></div>
<p><b>Note:</b> In this version of NUnit, the XML editor is somewhat primitive.
Errors in XML formatting are caught and an error message displayed. However,
the values of attributes are not validated as they are in the property-based
view and it is possible to create a project file, which NUnit is unable to
load. Improvements, including intellisense and better error handling, are
planned in future versions of the Project Editor.
</div>
<!-- Submenu -->
<div id="subnav">
<ul>
<li><a href="index.html">NUnit 2.6</a></li>
<ul>
<li><a href="getStarted.html">Getting Started</a></li>
<li><a href="writingTests.html">Writing Tests</a></li>
<li><a href="runningTests.html">Running Tests</a></li>
<ul>
<li><a href="nunit-console.html">Console Runner</a></li>
<li><a href="nunit-gui.html">Gui Runner</a></li>
<li><a href="pnunit.html">PNUnit Runner</a></li>
<li><a href="nunit-agent.html">NUnit Agent</a></li>
<li id="current"><a href="projectEditor.html">Project Editor</a></li>
<li><a href="runtimeSelection.html">Runtime Selection</a></li>
<li><a href="assemblyIsolation.html">Assembly Isolation</a></li>
<li><a href="configFiles.html">Configuration Files</a></li>
<li><a href="multiAssembly.html">Multiple Assemblies</a></li>
<li><a href="vsSupport.html">Visual Studio Support</a></li>
</ul>
<li><a href="extensibility.html">Extensibility</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>
<li><a href="vsTestAdapter.html">NUnit Test Adapter 0.90</a></li>
<ul>
<li><a href="vsTestAdapterLicense.html">License</a></li>
</ul>
<li><a href="&r=2.6.html"></a></li>
<li><a href="&r=2.6.html"></a></li>
</ul>
</div>
<!-- End of Submenu -->
<!-- Standard Footer for NUnit.org -->
<div id="footer">
Copyright © 2012 Charlie Poole. All Rights Reserved.
</div>
<!-- End of Footer -->
</body>
</html>
|