You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by js...@apache.org on 2006/05/25 19:19:04 UTC
svn commit: r409417 - /incubator/activemq/site/example-testing-scenario.html
Author: jstrachan
Date: Thu May 25 10:19:02 2006
New Revision: 409417
URL: http://svn.apache.org/viewvc?rev=409417&view=rev
Log:
Latest export from confluence
Modified:
incubator/activemq/site/example-testing-scenario.html
Modified: incubator/activemq/site/example-testing-scenario.html
URL: http://svn.apache.org/viewvc/incubator/activemq/site/example-testing-scenario.html?rev=409417&r1=409416&r2=409417&view=diff
==============================================================================
--- incubator/activemq/site/example-testing-scenario.html (original)
+++ incubator/activemq/site/example-testing-scenario.html Thu May 25 10:19:02 2006
@@ -245,11 +245,15 @@
<P>Assuming that all the test code is within a single Maven POM for now (e.g. activemq-integration-test version 4.0) which will deal with all the classpath issues.</P>
-<H3><A name="ExampleTestingScenario-Realsimpleversion"></A>Real simple version</H3>
+<P>We'll try describe the different ways this could work and give each implementation style a name so we can start revving different ways to solve this...</P>
-<P>Here the build knows what to do; each test case generates an XML file which becomes a named deployment artifact.</P>
+<H3><A name="ExampleTestingScenario-Headlessbuild"></A>Headless build</H3>
-<P>We use the following boxes...</P>
+<P>In this version there is no 'controller'; each build is considered to be a totally separate build.</P>
+
+<P>Each build knows what to do; each test case generates an XML file which becomes a named deployment artifact.</P>
+
+<P>e.g. imagine the following builds (which are really just running Java executables within a POM for classpath)</P>
<TABLE class="confluenceTable"><TBODY>
<TR>
@@ -274,12 +278,14 @@
</TR>
</TBODY></TABLE>
+<P>In the above example - each build has to kinda wait for other things to start up to some time period. e.g. the producer and consumer wanna keep around for say 5 minutes trying to connect to the broker as they can be started in any order.</P>
+
-<H3><A name="ExampleTestingScenario-Controllerversion"></A>Controller version</H3>
+<H3><A name="ExampleTestingScenario-Controllerbuild"></A>Controller build</H3>
-<P>Here the build is a master controller which spins off separate processes in a workflow</P>
+<P>The idea with the controller version is one of the tests (which is spun off first to try help) tries to coordinate among the test nodes.</P>
-<P>We use the following boxes...</P>
+<P>e.g. we could spin the controller first...</P>
<TABLE class="confluenceTable"><TBODY>
<TR>
@@ -318,7 +324,12 @@
<TD class="confluenceTd">java org.apache.activemq.test.ProducerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616</TD>
</TR>
</TBODY></TABLE>
-</DIV>
+
+<H3><A name="ExampleTestingScenario-Controllerfactorybuild"></A>Controller factory build</H3>
+
+<P>Fairly soon we're gonna have tons of builds firing off. We may want a single project to build with a raft of different test suites. Each single distributed integration/system/performance test might have many sub-builds (processes) to run.</P>
+
+<P>So we might want to run a single JUnit test case </P></DIV>
</DIV>
</TD>
@@ -329,7 +340,7 @@
<DIV id="site-footer">
Added by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=jstrachan">James Strachan</A>,
last edited by <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=jstrachan">James Strachan</A> on May 25, 2006
- (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=6131&originalId=6132">view change</A>)
+ (<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=6131&originalId=6133">view change</A>)
(<A href="http://goopen.org/confluence/pages/editpage.action?pageId=6131">edit page</A>)
</DIV>