Author: buildbot
Date: Wed Aug 15 11:55:00 2012
New Revision: 829006
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 11:55:00 2012
@@ -1 +1 @@
-1373348
+1373356
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
11:55:00 2012
@@ -251,7 +251,8 @@
<p>Having explained that our test depends upon the 'UserAdmin' service, and
that its a required dependency, means that our test won't run if this service
is not available<sup id="fnref:5"><a href="#fn:5"
rel="footnote">5</a></sup>.</p>
-<p>Sometimes, you need to do some additional set up before or after the
dependencies are resolved. For example, one might need to provision some
configuration in order to get dependencies in the correct state, or wait until
some other condition is met after all dependencies have been resolved. In order
to do this, one can override the <code>before()</code> or <code>after()</code>
methods in <code>IntegrationTestBase</code>. For our simple integration test,
however, we do not need such "advanced" set up.</p>
+<p>Sometimes, you need to do some additional set up before or after the
dependencies are resolved. For example, one might need to provision some
configuration in order to get dependencies in the correct state, or wait until
some other condition is met after all dependencies have been resolved. In order
to do this, one can override the <code>before()</code> or <code>after()</code>
methods<sup id="fnref:6"><a href="#fn:6" rel="footnote">6</a></sup> in
<code>IntegrationTestBase</code>.<br />
+For our simple integration test, however, we do not need such "advanced" set
up.</p>
<p>The only thing left is the actual test itself. As the 'UserAdmin' service
is being tracked for us, we can simply direct use it in our test:</p>
<div class="codehilite"><pre><span class="kd">public</span> <span
class="kd">class</span> <span class="nc">UserAdminIntegrationTest</span> <span
class="kd">extends</span> <span class="n">IntegrationTestBase</span> <span
class="o">{</span>
<span class="c1">// ...</span>
@@ -294,6 +295,9 @@
<li id="fn:5">
<p>To be more precise: the test will wait a couple of seconds to allow all
dependencies to be satisfied. If after this waiting period any dependency is
not satisfied, the test will fail. <a href="#fnref:5" rev="footnote"
title="Jump back to footnote 5 in the text">↩</a></p>
</li>
+<li id="fn:6">
+<p>The naming of these methods could use a second thought, see also:
https://issues.apache.org/jira/browse/ACE-289 <a href="#fnref:6"
rev="footnote" title="Jump back to footnote 6 in the text">↩</a></p>
+</li>
</ol>
</div></div>
<hr>
