deltaspike-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsme...@apache.org
Subject svn commit: r1682851 [3/3] - /deltaspike/site/trunk/content/staging/documentation/
Date Mon, 01 Jun 2015 09:41:36 GMT
Modified: deltaspike/site/trunk/content/staging/documentation/test-control.html
URL: http://svn.apache.org/viewvc/deltaspike/site/trunk/content/staging/documentation/test-control.html?rev=1682851&r1=1682850&r2=1682851&view=diff
==============================================================================
--- deltaspike/site/trunk/content/staging/documentation/test-control.html (original)
+++ deltaspike/site/trunk/content/staging/documentation/test-control.html Mon Jun  1 09:41:35
2015
@@ -281,7 +281,7 @@ table.CodeRay td.code>pre{padding:0}
 </div>
 </div>
 <div class="sect1">
-<h2 id="_configure_your_projects">Configure Your Projects</h2>
+<h2 id="_project_setup">Project Setup</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The configuration information provided here is for Maven-based projects and it assumes
that you have already declared the DeltaSpike version and DeltaSpike Core module for your
projects, as detailed in <a href="configure.html">Configure DeltaSpike in Your Projects</a>.
For Maven-independent projects, see <a href="configure.html#config-maven-indep">Configure
DeltaSpike in Maven-independent Projects</a>.</p>
@@ -395,12 +395,10 @@ of dependencies instead of the OpenWebBe
 </div>
 </div>
 <div class="sect1">
-<h2 id="_use_the_module_features">Use the Module Features</h2>
+<h2 id="_automated_container_booting_and_shutdown">Automated Container Booting and
Shutdown</h2>
 <div class="sectionbody">
 <div class="sect2">
-<h3 id="_automated_container_booting_and_shutdown">Automated Container Booting and
Shutdown</h3>
-<div class="sect3">
-<h4 id="_cditestrunner">CdiTestRunner</h4>
+<h3 id="_cditestrunner">CdiTestRunner</h3>
 <div class="paragraph">
 <p>Start and stop the CDI container automatically per test class with CdiTestRunner,
a JUnit Test-Runner.
 This also starts and stops one request and session per test-method.</p>
@@ -425,8 +423,8 @@ This also starts and stops one request a
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_cditestsuiterunner">CdiTestSuiteRunner</h4>
+<div class="sect2">
+<h3 id="_cditestsuiterunner">CdiTestSuiteRunner</h3>
 <div class="paragraph">
 <p>Extend automated CDI container start and stop actions to whole test suites with
CdiTestSuiteRunner, a JUnit Test-Suite-Runner.</p>
 </div>
@@ -444,17 +442,19 @@ This also starts and stops one request a
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_optional_shutdown_configuration">Optional Shutdown Configuration</h4>
+<div class="sect2">
+<h3 id="_optional_shutdown_configuration">Optional Shutdown Configuration</h3>
 <div class="paragraph">
 <p>You can set <code>deltaspike.testcontrol.stop_container</code> to <code>false</code>
(via the standard DeltaSpike config), resulting in the CDI Container being started just once
for all tests.</p>
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_test_customization">Test Customization</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_test_customization">Test Customization</h3>
-<div class="sect3">
-<h4 id="__testcontrol">@TestControl</h4>
+<h3 id="__testcontrol">@TestControl</h3>
 <div class="paragraph">
 <p>Customize the default behavior of CdiTestRunner with @TestControl. In the following
 case only one session for all test-methods (of the test-class) will be
@@ -472,8 +472,8 @@ created.</p>
 </div>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_projectstage_control">ProjectStage Control</h4>
+<div class="sect2">
+<h3 id="_projectstage_control">ProjectStage Control</h3>
 <div class="paragraph">
 <p>Override the default ProjectStage for unit tests with <code>ProjectStage.UnitTest.class</code>.</p>
 </div>
@@ -498,8 +498,10 @@ created.</p>
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_optional_configuration">Optional Configuration</h3>
+</div>
+<div class="sect1">
+<h2 id="_optional_configuration">Optional Configuration</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>From DeltaSpike 1.2, it is possible to provide a configuration for the underlying
test-container.
 However, currently only the adapter for OpenEJB embedded (available in CDI-Control) supports
it out-of-the-box.
@@ -510,8 +512,8 @@ The content of the file are key/value pa
 Therefore, it is a configuration which is not used by DeltaSpike itself
 (it is just forwarded (as it is) to the underlying test-container).</p>
 </div>
-<div class="sect3">
-<h4 id="_reconfigure_the_config_file_name_or_location">Reconfigure the config-file
Name or Location</h4>
+<div class="sect2">
+<h3 id="_reconfigure_the_config_file_name_or_location">Reconfigure the config-file
Name or Location</h3>
 <div class="paragraph">
 <p>If you would like to point to an existing config-file, you have to add for example:</p>
 </div>
@@ -533,10 +535,12 @@ Therefore, it is a configuration which i
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_optional_integrations">Optional Integrations</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_optional_integrations">Optional Integrations</h3>
-<div class="sect3">
-<h4 id="_mock_frameworks">Mock Frameworks</h4>
+<h3 id="_mock_frameworks">Mock Frameworks</h3>
 <div class="paragraph">
 <p>From DeltaSpike 1.0, it is possible to mock CDI-Beans. Usually @Exclude (+
 ProjectStage) is enough, however, for some cases mocked beans might be
@@ -738,8 +742,8 @@ mocked implementation via <code>@Exclude
 constructor) and specify the target-type via <code>@TypedMock</code>.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_jsf_via_myfaces_test">JSF (via MyFaces-Test)</h4>
+<div class="sect2">
+<h3 id="_jsf_via_myfaces_test">JSF (via MyFaces-Test)</h3>
 <div class="paragraph">
 <p>add on of</p>
 </div>
@@ -770,8 +774,10 @@ constructor) and specify the target-type
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_using_jersey_test_with_test_control">Using jersey-test with test-control</h3>
+</div>
+<div class="sect1">
+<h2 id="_using_jersey_test_with_test_control">Using jersey-test with test-control</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Jersey-test starts jetty which answers requests in a separated thread. Since ds
test-control just handles the thread of the test itself, it&#8217;s needed to integrate
jetty and jersey with the cdi-container. Usually that&#8217;s done via a ServletRequestListener
- the following part describes an alternative approach for jersey-test:</p>
 </div>
@@ -855,8 +861,10 @@ cdiHandlerWrapper.setHandler(<span class
 </div>
 </div>
 </div>
-<div class="sect2">
-<h3 id="_mixed_tests">Mixed Tests</h3>
+</div>
+<div class="sect1">
+<h2 id="_mixed_tests">Mixed Tests</h2>
+<div class="sectionbody">
 <div class="paragraph">
 <p>Usually you should have one kind of tests per test-module. However, if
 you need to add, for example, a test without an external-container to your
@@ -874,10 +882,12 @@ with:</p>
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_known_restrictions">Known Restrictions</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_known_restrictions">Known Restrictions</h3>
-<div class="sect3">
-<h4 id="_liquibase">Liquibase</h4>
+<h3 id="_liquibase">Liquibase</h3>
 <div class="paragraph">
 <p>Liquibase invokes <code>#toString</code> in a <code>AfterDeploymentValidation</code>
observer.
 <strong>that is not portable</strong> and therefore you have to deactivate the
@@ -905,8 +915,8 @@ mocking-support via:</p>
 <p>Further details are available at deactivatable.</p>
 </div>
 </div>
-<div class="sect3">
-<h4 id="_gradle">Gradle</h4>
+<div class="sect2">
+<h3 id="_gradle">Gradle</h3>
 <div class="paragraph">
 <p>Gradle by default does not put resources and compiled sources in to the same directory.
 When running a test using Gradle, this means your classes will not be in bean archives as
@@ -929,10 +939,12 @@ for resources to point to where the comp
 </div>
 </div>
 </div>
+</div>
+<div class="sect1">
+<h2 id="_spi">SPI</h2>
+<div class="sectionbody">
 <div class="sect2">
-<h3 id="_spi">SPI</h3>
-<div class="sect3">
-<h4 id="_externalcontainer">ExternalContainer</h4>
+<h3 id="_externalcontainer">ExternalContainer</h3>
 <div class="paragraph">
 <p>org.apache.deltaspike.testcontrol.spi.ExternalContainer allows to
 integrate containers which get started after the CDI container.
@@ -948,7 +960,6 @@ Currently DeltaSpike provides:</p>
 </div>
 </div>
 </div>
-</div>
             </div>
         </div>
 
@@ -983,7 +994,7 @@ Currently DeltaSpike provides:</p>
                     <div class="fallback-toc">
                         <ul class="sectlevel1">
 <li><a href="#_overview">Overview</a></li>
-<li><a href="#_configure_your_projects">Configure Your Projects</a>
+<li><a href="#_project_setup">Project Setup</a>
 <ul class="sectlevel2">
 <li><a href="#_1_declare_test_control_module_dependencies">1. Declare Test-Control
Module Dependencies</a></li>
 <li><a href="#_2_declare_cdi_implementation_specific_dependencies">2. Declare
CDI-implementation-specific dependencies</a>
@@ -996,28 +1007,26 @@ Currently DeltaSpike provides:</p>
 <li><a href="#_3_complete_additional_project_configuration">3. Complete Additional
Project Configuration</a></li>
 </ul>
 </li>
-<li><a href="#_use_the_module_features">Use the Module Features</a>
-<ul class="sectlevel2">
 <li><a href="#_automated_container_booting_and_shutdown">Automated Container
Booting and Shutdown</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_cditestrunner">CdiTestRunner</a></li>
 <li><a href="#_cditestsuiterunner">CdiTestSuiteRunner</a></li>
 <li><a href="#_optional_shutdown_configuration">Optional Shutdown Configuration</a></li>
 </ul>
 </li>
 <li><a href="#_test_customization">Test Customization</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#__testcontrol">@TestControl</a></li>
 <li><a href="#_projectstage_control">ProjectStage Control</a></li>
 </ul>
 </li>
 <li><a href="#_optional_configuration">Optional Configuration</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_reconfigure_the_config_file_name_or_location">Reconfigure the
config-file Name or Location</a></li>
 </ul>
 </li>
 <li><a href="#_optional_integrations">Optional Integrations</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_mock_frameworks">Mock Frameworks</a></li>
 <li><a href="#_jsf_via_myfaces_test">JSF (via MyFaces-Test)</a></li>
 </ul>
@@ -1025,19 +1034,17 @@ Currently DeltaSpike provides:</p>
 <li><a href="#_using_jersey_test_with_test_control">Using jersey-test with test-control</a></li>
 <li><a href="#_mixed_tests">Mixed Tests</a></li>
 <li><a href="#_known_restrictions">Known Restrictions</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_liquibase">Liquibase</a></li>
 <li><a href="#_gradle">Gradle</a></li>
 </ul>
 </li>
 <li><a href="#_spi">SPI</a>
-<ul class="sectlevel3">
+<ul class="sectlevel2">
 <li><a href="#_externalcontainer">ExternalContainer</a></li>
 </ul>
 </li>
 </ul>
-</li>
-</ul>
                     </div>
                 
             </div>



Mime
View raw message