Author: jawi
Date: Wed Aug 15 12:03:37 2012
New Revision: 1373361
URL: http://svn.apache.org/viewvc?rev=1373361&view=rev
Log:
Again formatting...
Modified:
ace/site/trunk/content/dev-doc/writing-tests.mdtext
Modified: ace/site/trunk/content/dev-doc/writing-tests.mdtext
URL:
http://svn.apache.org/viewvc/ace/site/trunk/content/dev-doc/writing-tests.mdtext?rev=1373361&r1=1373360&r2=1373361&view=diff
==============================================================================
--- ace/site/trunk/content/dev-doc/writing-tests.mdtext (original)
+++ ace/site/trunk/content/dev-doc/writing-tests.mdtext Wed Aug 15 12:03:37 2012
@@ -47,7 +47,7 @@ This snippet shows us almost all importa
* 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>. **Note:** the `alwaysRun = true` is needed to ensure that
this method is run, even though it does not belong to any test-group;
* 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;
-* 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.
+* 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.
To run the unit tests for a project, you simply go to the root directory of
the project itself, and call:
@@ -128,7 +128,7 @@ That is it! The only thing left is to ru
:::sh
$ ant test
-When running Eclipse, you can also run your integration test by right clicking
on it, and selecting `Run As -> OSGi JUnit Test` from its context menu.
+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.
## Notes
