State of our failing tests
jmesnil May 21, 2008 5:36 AMAs we race towards JBM2 alpha, I did some investigation on our current failing tests.
Some are failing because of missing features (ping, message chunk) or identified issues (security checks, unicod encodings).
The rest of the failing bugs seems related to acknowledgement & redelivery issues
Related to disabled ping mechanism:
org.jboss.messaging.tests.integration.core.remoting.impl.ClientCrashTest.testCrashClientWithOneConnection
org.jboss.messaging.tests.integration.core.remoting.impl.ClientCrashTest.testCrashClientWithTwoConnections
org.jboss.messaging.tests.integration.core.remoting.mina.ClientKeepAliveTest.testKeepAliveWithClientOK
org.jboss.messaging.tests.integration.core.remoting.mina.ClientKeepAliveTest.testKeepAliveWithClientNotResponding
org.jboss.messaging.tests.integration.core.remoting.mina.ClientKeepAliveTest.testKeepAliveWithClientTooLongToRespond
org.jboss.messaging.tests.integration.core.remoting.mina.ClientKeepAliveTest.testKeepAliveWithClientRespondingAndClientNotResponding
org.jboss.messaging.tests.integration.core.remoting.mina.ServerKeepAliveTest.testKeepAliveWithServerNotResponding
org.jboss.messaging.tests.integration.core.remoting.mina.ServerKeepAliveTest.testKeepAliveWithServerSessionFailed
org.jboss.messaging.tests.unit.jms.network.ClientNetworkFailureTest.testServerResourcesCleanUpWhenClientCommThrowsException
org.jboss.messaging.tests.unit.jms.network.ClientNetworkFailureTest.testServerResourcesCleanUpWhenClientCommDropsPacket
Related to message chunk:
org.jboss.test.messaging.jms.String64KLimitTest.test64KLimitWithTextMessage
org.jboss.test.messaging.jms.String64KLimitTest.test64KLimitWithObjectMessage
Related to security check on one-way messages:
org.jboss.test.messaging.jms.SecurityTest.testInvalidTopicPublisher
org.jboss.test.messaging.jms.SecurityTest.testInvalidQueueSender
org.jboss.test.messaging.jms.SecurityTest.testDefaultSecurityInvalid
Related to Unicode encodings:
org.jboss.test.messaging.jms.message.MessageBodyTest.testMapMessage
org.jboss.messaging.tests.unit.core.util.SimpleStringTest.testUnicode
Related to Journal
org.jboss.messaging.tests.unit.core.journal.impl.FakeJournalImplTest.testReclaimTransactionalAddCommit
org.jboss.messaging.tests.unit.core.journal.impl.FakeJournalImplTest.testCommitRecordsInFileNoReclaim
org.jboss.messaging.tests.unit.core.journal.impl.FakeJournalImplTest.testPrepareNoReclaim
org.jboss.messaging.tests.unit.core.journal.impl.FakeJournalImplTest.testRollbackRecordsInFileNoReclaim
org.jboss.messaging.tests.unit.core.journal.impl.FakeJournalImplTest.testPrepareReclaim
Not investigated
org.jboss.test.messaging.jms.MessageConsumerTest.testRedelMessageListener2
org.jboss.test.messaging.jms.message.BytesMessageTest.testRedelivery
org.jboss.test.messaging.jms.AcknowledgementTest.testMessageListenerClientAck
org.jboss.test.messaging.jms.AcknowledgementTest.testMessageListenerTransactionalAck
org.jboss.test.messaging.jms.AcknowledgementTest.testAutoAcknowledge
org.jboss.test.messaging.jms.AcknowledgementTest.testDupsOKAcknowledgeQueue
org.jboss.test.messaging.jms.AcknowledgementTest.testMessageListenerAutoAck
org.jboss.test.messaging.jms.AcknowledgementTest.testMessageListenerDupsOK
org.jboss.test.messaging.jms.CTSMiscellaneousTest.testNonPersistentMessagesSentSynchronously
org.jboss.test.messaging.jms.MessageConsumerTest.testExceptionMessageListener1
org.jboss.test.messaging.jms.MessageConsumerTest.testExceptionMessageListener2