Author: buildbot
Date: Wed Aug 15 12:03:41 2012
New Revision: 829011
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/dev-doc/writing-tests.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Aug 15 12:03:41 2012
@@ -1 +1 @@
-1373360
+1373361
Modified: websites/staging/ace/trunk/content/dev-doc/writing-tests.html
==============================================================================
--- websites/staging/ace/trunk/content/dev-doc/writing-tests.html (original)
+++ websites/staging/ace/trunk/content/dev-doc/writing-tests.html Wed Aug 15
12:03:41 2012
@@ -205,7 +205,7 @@
<ul>
<li>The <tt>@BeforeMethod</tt> annotation allows us to run a method before
each individual test. In this 'setUp' method, we create a stub implementation
of a <tt>LogService</tt>. <strong>Note:</strong> the <code>alwaysRun =
true</code> is needed to ensure that this method is run, even though it does
not belong to any test-group;</li>
<li>The method <tt>testAuthenticateFailsWithNullContext</tt> is annotated with
the <tt>@Test</tt> annotation, and its parameters tell us two more things: it
belongs to a group UNIT, and there's a failure to expect in the form of an
'IllegalArgumentException'. In this method, we instantiate the class-under-test
(using the stub 'LogService') and invoke a method on it;</li>
-<li>The last method (<tt>testAuthenticateFailsWithoutAuthProcessors<tt>) shows
us how to make assertions on the results of methods. The <tt>Assert</tt> class
of TestNG is almost equivalent to its equally named counterpart in JUnit with
one difference: the failure message always comes last.</li>
+<li>The last method (<tt>testAuthenticateFailsWithoutAuthProcessors</tt>)
shows us how to make assertions on the results of methods. The <tt>Assert</tt>
class of TestNG is almost equivalent to its equally named counterpart in JUnit
with one difference: the failure message always comes last.</li>
</ul>
<p>To run the unit tests for a project, you simply go to the root directory of
the project itself, and call:</p>
<div class="codehilite"><pre><span class="nv">$ </span>ant testng
@@ -275,7 +275,7 @@ For our simple integration test, however
</pre></div>
-<p>When running Eclipse, you can also run your integration test by right
clicking on it, and selecting <code>Run As -> OSGi JUnit Test</code> from
its context menu.</p>
+<p>When running Eclipse, you can also run your integration test by right
clicking on it, and selecting <tt>Run As -> OSGi JUnit Test</tt> from its
context menu.</p>
<h2 id="notes">Notes</h2>
<div class="footnote">
<hr />
