You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/04 14:29:38 UTC

[jira] [Assigned] (QPID-3713) Remove redundant failover test from Java system test suite.

     [ https://issues.apache.org/jira/browse/QPID-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall reassigned QPID-3713:
--------------------------------

    Assignee: Robbie Gemmell  (was: Keith Wall)

Hi Robbie, could you review this change please?
                
> Remove redundant failover test from Java system test suite.
> -----------------------------------------------------------
>
>                 Key: QPID-3713
>                 URL: https://issues.apache.org/jira/browse/QPID-3713
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Tests
>            Reporter: Keith Wall
>            Assignee: Robbie Gemmell
>             Fix For: 0.15
>
>
> The Java test suite contains a number of failover tests that duplicate the new tests introduced by the recent failover work.   This task is to remove redundant tests.
> The following tests/test cases have been identified:
> * QueueBrowserAutoAckTest#testFailover*. These tests were running against Java 0-9-1 profiles and excluded against Java/CPP 0-10. New test cases FailoverBehaviourTest#testTransactedQueueBrowserCloseWhileFailover/testClientAcknowledge test the same code paths.
> * AcknowledgeAfterFailoverOnMessageTest/AcknowledgeAfterFailoverTest. These tests were globally excluded (Excludes file).  New tests FBT.testClientAcknowledgedSessionCloseAfterFailover/testTransactedSessionCloseAfterFailover/testAcknowledgeAfterFailoverForAsynchronousConsumer cover these scenarios.
> * MessageDisappearWithIOExceptionTest. Tests were added after a defect arising from Java Broker use of MINA.  Test scenario covered by FBT.testRecoverAfterFailoverInAutoAcknowledgeMode.
> * FailoverBeforeConsumingRecoverTest.  Test case seemed weak: merely caused a failover then repeated the same tests as its super (RecoverTest). FBT.testRecoverAfterFailover and testRecoverWithConsumedMessagesAfterFailover are superior replacements.
> * QuickAcking. Test exercised same code paths as FBT.testMessageProducingAndRollbackAfterFailover.
> * CloseAfterConnectionFailureTest duplicates FailoverMethodTest#testNoFailover. The testcase was actually excluded from all profiles.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org