6:40 a.m.
I'm trying to locate the MDB integration tests.
I have found a few in jboss-head/testsuite/src/main/org/jboss/test/mdb
which test using the old JMSContainerInvoker.
Although I am not sure whether they are worthy of being called
integration tests since test coverage is shockingly poor. Note the comment:
/**
* Some simple tests of MDB. These could be much more elaborated.
*
* In the future at least the following tests should be done some how:
* <ol>
* <li>Queue
* <li>Topic
* <li>Durable topic
* <li>Bean TX - with AUTO_ACK and DUPS_OK
* <li>CMT Required
* <li>CMT NotSupported
* <li>Selector
* <li>User and password login
* <li>Al the stuff with the context
* </ol>
I am also trying to find the equivalent tests which test using JCA1.5
message inflow, but I can't find any.
I guess they must be somewhere.
Can someone point me in the right direction?
--
Tim Fox
JBoss Messaging Technical Lead
JBoss - a division of Red Hat
T: +44 2088006768
M: +44 7957983205
E: tim.fox(a)jboss.com tim.fox(a)redhat.com
12:19 p.m.
They are spread out. Other mdb tests are:
testsuite module:
org.jboss.test.cts.test.MDBUnitTestCase
org.jboss.test.jca.test.InflowUnitTestCase
ejb3 module:
org.jboss.ejb3.test.mdb
org.jboss.ejb3.test.mdbtopic
org.jboss.ejb3.test.mdbtransactions
Tim Fox wrote:
I'm trying to locate the MDB integration tests.
I have found a few in jboss-head/testsuite/src/main/org/jboss/test/mdb
which test using the old JMSContainerInvoker.
Although I am not sure whether they are worthy of being called
integration tests since test coverage is shockingly poor. Note the comment:
/**
* Some simple tests of MDB. These could be much more elaborated.
*
* In the future at least the following tests should be done some how:
* <ol>
* <li>Queue
* <li>Topic
* <li>Durable topic
* <li>Bean TX - with AUTO_ACK and DUPS_OK
* <li>CMT Required
* <li>CMT NotSupported
* <li>Selector
* <li>User and password login
* <li>Al the stuff with the context
* </ol>
I am also trying to find the equivalent tests which test using JCA1.5
message inflow, but I can't find any.
I guess they must be somewhere.
Can someone point me in the right direction?
12:48 p.m.
The coverage still seems very poor w.r.t. integration tests, unless I'm
missing something.
From the point of view of JBM (and JBossMQ) we need to know all the
main use cases are tests with the JMSContainerInvoker, and also using
JCA1.5 inflow now this is apparently supported in production.
Without proper coverage we can't have any confidence that JBM (or
JBossMQ) will work correctly with the app server.
I've added a task to get these tests sorted before we release JBM 1.2.
Scott M Stark wrote:
They are spread out. Other mdb tests are:
testsuite module:
org.jboss.test.cts.test.MDBUnitTestCase
org.jboss.test.jca.test.InflowUnitTestCase
ejb3 module:
org.jboss.ejb3.test.mdb
org.jboss.ejb3.test.mdbtopic
org.jboss.ejb3.test.mdbtransactions
Tim Fox wrote:
> I'm trying to locate the MDB integration tests.
>
> I have found a few in jboss-head/testsuite/src/main/org/jboss/test/mdb
> which test using the old JMSContainerInvoker.
>
> Although I am not sure whether they are worthy of being called
> integration tests since test coverage is shockingly poor. Note the comment:
>
> /**
> * Some simple tests of MDB. These could be much more elaborated.
> *
> * In the future at least the following tests should be done some how:
> * <ol>
> * <li>Queue
> * <li>Topic
> * <li>Durable topic
> * <li>Bean TX - with AUTO_ACK and DUPS_OK
> * <li>CMT Required
> * <li>CMT NotSupported
> * <li>Selector
> * <li>User and password login
> * <li>Al the stuff with the context
> * </ol>
>
> I am also trying to find the equivalent tests which test using JCA1.5
> message inflow, but I can't find any.
>
> I guess they must be somewhere.
>
> Can someone point me in the right direction?
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Tim Fox
JBoss Messaging Technical Lead
JBoss - a division of Red Hat
T: +44 2088006768
M: +44 7957983205
E: tim.fox(a)jboss.com tim.fox(a)redhat.com
12:53 p.m.
Your right.
Tim Fox wrote:
The coverage still seems very poor w.r.t. integration tests, unless
I'm
missing something.
From the point of view of JBM (and JBossMQ) we need to know all the main
use cases are tests with the JMSContainerInvoker, and also using JCA1.5
inflow now this is apparently supported in production.
Without proper coverage we can't have any confidence that JBM (or
JBossMQ) will work correctly with the app server.
I've added a task to get these tests sorted before we release JBM 1.2.
8:44 a.m.
Scott M Stark wrote:
> They are spread out. Other mdb tests are:
>
> testsuite module:
> org.jboss.test.cts.test.MDBUnitTestCase
> org.jboss.test.jca.test.InflowUnitTestCase
>
> ejb3 module:
> org.jboss.ejb3.test.mdb
> org.jboss.ejb3.test.mdbtopic
> org.jboss.ejb3.test.mdbtransactions
>
On Sat, 2007-01-13 at 18:48 +0000, Tim Fox wrote:
The coverage still seems very poor w.r.t. integration tests, unless I'm
missing something.
That is true of org.jboss.test.mdb
I remember complaining about them 3 years ago, they are not good tests.
I only left them in place because you can never have too many tests. :-)
The real tests are in org.jboss.test.messagedriven
Theses tests use a framework that creates the same tests for
old = JMSContainerInvoker
new = JCA Inflow
They have a simple format:
properties - for configuration of the activiation spec or the invoker
proxy
operation - steps in the test (including assertions)
See org.jboss.test.messagedriven.support.BaseMessageDrivenTest
public void runTest(Operation[] ops, Properties props) throws
So you can trivially add new tests without having to create
new MDB deployments for each test.
e.g. The single mdb for JCA1.5 looks like this:
<message-driven>
<ejb-name>TestMDB</ejb-name>
<activation-config>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>${test.messagedriven.destination}</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>${test.messagedriven.destinationType}</activation-config-property-value>
</activation-config-property>
etc....
But they are incomplete until this task is done:
http://jira.jboss.com/jira/browse/JBAS-1434
From the point of view of JBM (and JBossMQ) we need to know all the
main use cases are tests with the JMSContainerInvoker, and also using
JCA1.5 inflow now this is apparently supported in production.
Without proper coverage we can't have any confidence that JBM (or
JBossMQ) will work correctly with the app server.
I've added a task to get these tests sorted before we release JBM 1.2.
Is that this task?
http://jira.jboss.com/jira/browse/JBMESSAGING-170
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
8:51 a.m.
Ovidiu Feodorov wrote:
Adrian wrote:
> you can never have too many tests. :-)
>
Can we trademark this? :)
Ovidiu - I thought you already had some time ago? ;) Now you can sue Adrian.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Tim Fox
JBoss Messaging Technical Lead
JBoss - a division of Red Hat
T: +44 2088006768
M: +44 7957983205
E: tim.fox(a)jboss.com tim.fox(a)redhat.com
7022
days inactive
7026
days old
jboss-development@lists.jboss.org
6 comments
4 participants
participants (4)
-
Adrian -
Ovidiu Feodorov -
Scott M Stark -
Tim Fox