[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests

[Richard Achmatowicz (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12345823 ] 
            
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------

I've started to move testcases over, and things are progressing smoothly.

A number of the testcases move over with no change - in particular, those test cases which only assume the existence of a ConnectionFactory object in JNDI and which also make use of createTemporaryTopic()/createTemporaryQueue().

However, for the test cases I have encountered so far which make use of named topics and queues, I have found that these are all deployed dynamically by the test cases themselves - my making a call to JBossTestCase.getDeploySetup() and passing test-destinations-service.xml file. In fact, in Adrian's server configurations for JBossMQ, he only deploys one Queue, named DLQ. This is why all test destinations are deployed dynamically. 

In addition to this, some of the test cases rely on defined usernames and roles.

At present, the Messaging configuration does not match this arrangement, and if we are to keep the test cases more or less in their present state (i.e. keep existing deployments as they are, keep existing security related features as they are), we are going to have to rework the Messaging configuration to essentially match Adrian's JBossMQ configuration, in the following ways:

(i) ensure that only one Queue named DLQ is created by the AS at startup
(ii) create deployment descriptors for starting the test Topics and Queues (done)
(iii) add the users and roles which Adrian uses to messaging-roles.properties and messaging-users.properties

In order not to interfere with your use of the existing Messaging configuration with your tests (functional, stress, etc), it seems as though we need to add a target to release-admin.xml which builds a Messaging configuration for the AS testing. Does this sound reasonable?
 

 


> Separate generic JMS tests
> --------------------------
>
>                 Key: JBMESSAGING-555
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-555
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>         Assigned To: Richard Achmatowicz
>             Fix For: 1.2.0.Beta1
>
>
> Separate the generic JMS tests by creating a copy of all JBossMQ tests and eliminating the JBossMQ-specific ones. The remaining tests will be refactored so they can be run with both Messaging and JBossMQ,

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira