diff options
Diffstat (limited to 'tools/NUnit/doc/assertions.html')
| -rw-r--r-- | tools/NUnit/doc/assertions.html | 91 |
1 files changed, 91 insertions, 0 deletions
diff --git a/tools/NUnit/doc/assertions.html b/tools/NUnit/doc/assertions.html new file mode 100644 index 0000000..eed9c0b --- /dev/null +++ b/tools/NUnit/doc/assertions.html @@ -0,0 +1,91 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<!-- Standard Head Part -->
+<head>
+<title>NUnit - Assertions</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>Assertions</h2>
+
+<p>Assertions are central to unit testing in any of the xUnit frameworks, and NUnit
+ is no exception. NUnit provides a rich set of assertions as static methods of
+ the Assert class.</p>
+
+<p>If an assertion fails, the method call does not return and an error is reported.
+ If a test contains multiple assertions, any that follow the one that failed
+ will not be executed. For this reason, it's usually best to try for one
+ assertion per test.</p>
+
+<p>Each method may be called without a message, with a simple text message or with
+ a message and arguments. In the last case the message is formatted using the
+ provided text and arguments.</p>
+
+<h3>Two Models</h3>
+
+<p>Before NUnit 2.4, a separate method of the Assert class was used for each
+ different assertion. We call this the
+ <a href="classicModel.html">classic model</a>. It
+ continues to be supported in NUnit, since many people prefer it.</p>
+
+<p>Beginning with NUnit 2.4, a new
+ <a href="constraintModel.html">constraint-based model</a> is being
+ introduced. This approach uses a single method of the Assert class
+ for all assertions, passing a <b>constraint</b> object that specifies the
+ test to be performed.
+
+<p>This constraint-based model is now used internally by NUnit
+ for all assertions. The methods of the classic approach have been
+ re-implemented on top of this new model.
+</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 id="current"><a href="assertions.html">Assertions</a></li> +<ul> +<li><a href="classicModel.html">Classic Model</a></li> +<li><a href="constraintModel.html">Constraint Model</a></li> +</ul> +<li><a href="attributes.html">Attributes</a></li> +<li><a href="nunit-console.html">Console Runner</a></li> +<li><a href="nunit-gui.html">Gui Runner</a></li> +<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>
|