3:58 p.m.
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
3:37 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
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
6:36 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
Should these changes to the contents of the jboss-messaging.sar be performed in
release-admin.xml or in your build? They are changes to the files in the sar, and not any
changes relating to the default configuration, and so you have complete control over their
contents.
Changing these files in the sar would require introducing a different build artifact for
AS testing as opposed to your functional testing.
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
2:30 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
I added the following genric JMS test cases today:
[rachmatowicz@dev03 testsuite]$ svn commit -m "A set of refactored generic JMS test
cases"
Sending testsuite/build.xml
Sending testsuite/src/main/org/jboss/test/jbossmessaging/JMSTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/MockServerSessionPool.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/ConnectionConsumerUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/DuplicateClientIDUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/JBossJMSUnitTest.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/JBossSessionRecoverUnitTestCase.java
Adding testsuite/src/main/org/jboss/test/jbossmessaging/test/Jms11UnitTest.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/MessageBodyUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/MessageTypesUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/MessagingRefactoringUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/RollBackUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/SessionCloseStressTestCase.java
Sending testsuite/src/resources/jbossmessaging/provider.properties
Adding testsuite/src/resources/jbossmessaging/test-destinations-service.xml
Transmitting file data ...............
Committed revision 57858.
These test cases subclass from org.jboss.test.jbossmessaging.JMSTestCase.
They determine which Admin implementation to use by locating the resource
provider.properties and inspecting the property jms.provider.admin.class. They determine
which deployment to use by inspecting the property jms.provider.resources.dir in the same
file.
I have modified the file messaging-destinations-service.xml in the messaging server
configuration of jboss-messaging-scoped.sar to deploy only the Queue DLQ. All other
deployments are performed dynamically within the test cases.
There are some apparently bona fide failures of these test cases when they are executed.
I shall continue refactoring.
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
2:30 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
I also had to adjust the security properties in messaging-users.properties and
messaging-roles.properties.
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
9:06 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-555:
---------------------------------------------
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?
I would rather keep it separated. I see it more of a function of the testsuite build
script. The release admin does need not care of security roles in JBoss AS integration
test suite.
I can create the ant configuration script fragment for you to use, if you wish, it
shouldn't be any big deal
The changes should be applied post-deployment.
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
10:22 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
Yes, please, I would appreciate it if you could create the fragment. Because that fragment
will contain rexexp terms, which are messy and should not be present in-line in
testsuite/build.xml, i'll create a separate ant script containing your snippet and
place it in resources/jbossmessaging.
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
5:04 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
I've added another batch of test cases:
Adding testsuite/src/main/org/jboss/test/jbossmessaging/JMSBase.java
Adding testsuite/src/main/org/jboss/test/jbossmessaging/test/JoramUnitTestCase.java
Adding testsuite/src/main/org/jboss/test/jbossmessaging/test/SecurityUnitTestCase.java
Adding
testsuite/src/main/org/jboss/test/jbossmessaging/test/TemporarySessionConnectionUnitTestCase.java
Adding testsuite/src/main/org/jboss/test/jbossmessaging/test/UnackedUnitTestCase.java
Adding testsuite/src/main/org/jboss/test/jbossmessaging/test/XAResourceUnitTestCase.java
I am within 11 test cases of completing the refactoring. I am putting together a
spreadsheet of all JMS test cases
in the AS testsuite, summarising the test cases into three classes:
*which test cases are generic and easily refactored (these have already been comitted, as
above)
* which test cases are generic and less easy to refactor (this will need a bit of
consultation)
* which test cases are not generic and why
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
3:17 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
I have finished splitting the tests into generic and non-generic sets, and will upload the
spreadsheet after a review with Ryan.
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
5:10 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=all ]
Richard Achmatowicz updated JBMESSAGING-555:
--------------------------------------------
Attachment: ASTestCasesInventory.ods
I have now attached the file ASTestCasesInventory to this issue.
This spreadsheet summarises the split between generic and non-generic test cases.
1. Most of the test cases in the first section, Easily Refactored, have been refactored
and committed to the testsuite. Exception to this are the test cases in the package
jbossmq.stress, which have been in the testsuite but never executed for AS 3.2, 4.0 and
5.0.
2. The test cases in the second section, More Involved To Refactor, require a
'recovery' deployment, which was developed for JBossMQ. I'm mnot certain if
this can be duplicated within Messaging, so someone in Messaging will have to check it
before I can commit those refactored tests.
3. The third set are tests which I have found significant JBossMQ dependencies in. Some of
these tests test JBossMQ features, or use JBossMQ utility classes. Whether these need to
be rewritten or not is up to the Messaging group.
The refactored tests do have failures, which someone will need to look at at some point.
JBoss HEAD is in a poor state at the moment though, and has problems building. I'll
put up a list of the failures for you to see.
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
Attachments: ASTestCasesInventory.ods
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
10:06 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=comments#action_12... ]
Richard Achmatowicz commented on JBMESSAGING-555:
-------------------------------------------------
Here follows the output from running the refactored test cases against a JBAS instance
with JBossMQ replaced by scoped Messaging. The jbossmessaging.ra failures are due to a jar
problem which i'm looking at.
tests-jbossmessaging-unit:
[junit] Running org.jboss.test.jbossmessaging.perf.JMSPerfStressTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 15.375 sec
[junit] Running org.jboss.test.jbossmessaging.perf.JMSReconnectStressTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.994 sec
[junit] Running org.jboss.test.jbossmessaging.perf.ReceiveNackClientStressTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 3.648 sec
[junit] Test org.jboss.test.jbossmessaging.perf.ReceiveNackClientStressTestCase
FAILED
[junit] Running org.jboss.test.jbossmessaging.perf.SendReplyPerfStressTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.441 sec
[junit] Running org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.947 sec
[junit] Test org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.ra.RaQueueUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 1.899 sec
[junit] Test org.jboss.test.jbossmessaging.ra.RaQueueUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.ra.RaSyncRecUnitTestCase
[junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 0.543 sec
[junit] Test org.jboss.test.jbossmessaging.ra.RaSyncRecUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.ra.RaTopicUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 1.996 sec
[junit] Test org.jboss.test.jbossmessaging.ra.RaTopicUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.ConcurrentDeliveryUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 22.719 sec
[junit] Running org.jboss.test.jbossmessaging.test.ConnectionConsumerUnitTestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 2.437 sec
[junit] Running org.jboss.test.jbossmessaging.test.DuplicateClientIDUnitTestCase
[junit] Tests run: 3, Failures: 2, Errors: 0, Time elapsed: 1.752 sec
[junit] Test org.jboss.test.jbossmessaging.test.DuplicateClientIDUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.JBossSessionRecoverUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 12.793 sec
[junit] Test org.jboss.test.jbossmessaging.test.JBossSessionRecoverUnitTestCase
FAILED
[junit] Running org.jboss.test.jbossmessaging.test.JoramUnitTestCase
[junit] Tests run: 199, Failures: 9, Errors: 14, Time elapsed: 206.105 sec
[junit] Test org.jboss.test.jbossmessaging.test.JoramUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase
[junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 13.784 sec
[junit] Test org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.MessageTypesUnitTestCase
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 5.331 sec
[junit] Running org.jboss.test.jbossmessaging.test.MessagingRefactoringUnitTestCase
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.555 sec
[junit] Running org.jboss.test.jbossmessaging.test.RollBackUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 8.225 sec
[junit] Test org.jboss.test.jbossmessaging.test.RollBackUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.SecurityUnitTestCase
[junit] Tests run: 32, Failures: 12, Errors: 1, Time elapsed: 19.382 sec
[junit] Test org.jboss.test.jbossmessaging.test.SecurityUnitTestCase FAILED
[junit] Running
org.jboss.test.jbossmessaging.test.TemporarySessionConnectionUnitTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.186 sec
[junit] Running org.jboss.test.jbossmessaging.test.UnackedUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.jboss.test.jbossmessaging.test.UnackedUnitTestCase FAILED (timeout)
[junit] Running org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 2.487 sec
[junit] Test org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase FAILED
[junit] Running org.jboss.test.jbossmessaging.test.XAResourceWrapperSmokeUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.438 sec
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
Attachments: ASTestCasesInventory.ods
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
9:37 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=all ]
Ovidiu Feodorov updated JBMESSAGING-555:
----------------------------------------
Fix Version/s: 1.2.0.Beta2
(was: 1.2.0.Beta1)
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.Beta2
Attachments: ASTestCasesInventory.ods
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
12:34 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=all ]
Ovidiu Feodorov updated JBMESSAGING-555:
----------------------------------------
Fix Version/s: 1.2.0.CR1
(was: 1.2.0.Beta2)
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.CR1
Attachments: ASTestCasesInventory.ods
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
7:48 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=all ]
Ovidiu Feodorov updated JBMESSAGING-555:
----------------------------------------
Priority: Critical (was: Major)
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
Priority: Critical
Fix For: 1.2.0.CR1
Attachments: ASTestCasesInventory.ods
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
5:33 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-555) Separate generic JMS tests
[ http://jira.jboss.com/jira/browse/JBMESSAGING-555?page=all ]
Ovidiu Feodorov closed JBMESSAGING-555.
---------------------------------------
Resolution: Done
The generic JMS integration test framework works fine. There are individual tests that
fail, but I will create separated JIRA tasks for those.
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
Priority: Critical
Fix For: 1.2.0.CR1
Attachments: ASTestCasesInventory.ods
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
7112
days inactive
7259
days old
14 comments
3 participants
participants (3)
-
Ovidiu Feodorov (JIRA) -
Ovidiu Feodorov (JIRA) -
Richard Achmatowicz (JIRA)