diff options
Diffstat (limited to 'tools/NUnit/doc/nunit-agent.html')
-rw-r--r-- | tools/NUnit/doc/nunit-agent.html | 97 |
1 files changed, 97 insertions, 0 deletions
diff --git a/tools/NUnit/doc/nunit-agent.html b/tools/NUnit/doc/nunit-agent.html new file mode 100644 index 0000000..d5f8039 --- /dev/null +++ b/tools/NUnit/doc/nunit-agent.html @@ -0,0 +1,97 @@ +<!-- saved from url=(0014)about:internet --><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> +<html> +<!-- Standard Head Part --> +<head> +<title>NUnit - Nunit-agent</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-Agent</h2> + +<p>The nunit-agent.exe program is used by other runners when the tests are being + run in a separate process. It is not intended for direct execution by users. + +<p>NUnit runs tests in a separate process in several situations: + +<ol> +<li>When the program needs to be run under a different framework or version +from the one being used by NUnit itself. +<li>When the user requests process-level isolation through the command line +or the NUnit settings. +</ol> + +<h3>Debugging</h3> + +<p>When debugging tests that are run in a separate process, it is + not possible to do so by simply running the console or gui runner + under the debugger. Rather, it is necessary to attach the debugger + to the nunit-agent process after the tests have been loaded. + +<p>When running under the Gui, NUnit will continue to use the same + process to reload tests so that it is not normally necessary to + re-attach to a new process. However, if the settings are changed + in a way that requires a differnt process - for example, by changing + the version of the runtime that is being used - the old process will + be terminated and a new one created. In that case, it's necessary + to re-attach to the new process. + + +</div> + +<!-- Submenu --> +<div id="subnav"> +<ul> +<li><a href="index.html">NUnit 2.5.9</a></li> +<ul> +<li><a href="getStarted.html">Getting Started</a></li> +<li><a href="assertions.html">Assertions</a></li> +<li><a href="constraintModel.html">Constraints</a></li> +<li><a href="attributes.html">Attributes</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 id="current"><a href="nunit-agent.html">NUnit Agent</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> +</ul> +</div> +<!-- End of Submenu --> + + +<!-- Standard Footer for NUnit.org --> +<div id="footer"> + Copyright © 2010 Charlie Poole. All Rights Reserved. +</div> +<!-- End of Footer --> + +</body> +</html> |