Hi Ovidiu,
Started working on the test suite last week end.
(Had some issues with compiling the jmx module,hence the delay)
Here is the brief of the test suite structure
Location
${jboss-head}/jms/tests
Package :
org.jboss.test.messaging.jmsapi
org.jboss.test.messaging.jmsapi.connection
org.jboss.test.messaging.jmsapi.flow
org.jboss.test.messaging.jmsapi.message
...
Actors
All TestCases extend org.jboss.test.messaging.MessagingTestCase
| Provider specfic Subclasses of Abstract class
org.jboss.test.messaging.util.AdminUtility : responsible for getting the
initial context, binding /unbinding of the administered objects.
|
| Property file decides which subclass of this AdminUtility gets picked
up.Sub class instantiated using reflection to keep the code independent of teh
actual impl
|
| e.g
| org.jboss.test.messaging.util.provider.JBossMessAdminUtility extends
| org.jboss.test.messaging.util.AdminUtility
|
| JBossMessAdminUtility uses ServerWrapper internally(for the time being)
|
| org.jboss.test.messaging.util.provider.JBossMQAdminUtility : for JBossMQ..
|
|
|
| Let me know if this is ok,.
| {Will come out with the design proposal for the perofrmance test framework
in the other thread.}
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871734#3871734
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871734
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
