You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Jim Alateras <ji...@comware.com.au> on 2003/09/21 14:16:31 UTC

[merlin] Best Practice for writing merlin test cases.

Hi,

Is there a best practice for writing merlin test cases, specifically for
testing service interfaces.

cheers
</jima>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: [merlin] Best Practice for writing merlin test cases.

Posted by Stephen McConnell <mc...@apache.org>.

Jim Alateras wrote:

>Hi,
>
>Is there a best practice for writing merlin test cases, specifically for
>testing service interfaces.
>

Its a little eatrly to brand this as a best practice but here is what I do:

in mavenb.xml

<postGoal name="test:test">
   <attainGoal name="merlin:simulate/>
<postGoal>

In your project.properties file you can override the block and 
configration files to use if you need to. In you block descriptor 
declare you deployment scanario and a test component:

  <container name="whatever">
     <component name="batman" class="org.gotham-city.CrimeFighter"/>
     <component name="penguin" class="net.evil.CrimeWave"/>
  </container>

So lauching this block results in the deployment of Batman.  The Penquin 
should declare a dependecy on Batman (as part of its type defintion) and 
then when invoked (via initiaze, execute or start) should raise hell and 
brimestone on Batman in an attempt to bring down Gotham City to a 
standstill and the ultimate distruction of world's greatest super hero. 
If you want to get really nasty you can create multiple startable test 
components enabling evaluation of Batman's ability to do things like, 
walk and drink at the same time while defending Gotham City from the 
most evil person know to mankind.

Hoope that helps!

Cheers, Stephen.

>
>
>cheers
></jima>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org