diff options
| author | Keith Wall <kwall@apache.org> | 2011-12-26 18:59:29 +0000 |
|---|---|---|
| committer | Keith Wall <kwall@apache.org> | 2011-12-26 18:59:29 +0000 |
| commit | d7abfe5f7a518b3967dc52fb6babde6a3d5a8955 (patch) | |
| tree | 49e4a8fad8072c08f3501391f532a909b8e72a70 /java/client/src/test | |
| parent | 1141cce0ff7b5b8799371501820e1771a5e3d693 (diff) | |
| download | qpid-python-d7abfe5f7a518b3967dc52fb6babde6a3d5a8955.tar.gz | |
QPID-3713: remove redundant failover test cases
The following tests/test cases have been identified:
1) 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.
2) AcknowledgeAfterFailoverOnMessageTest/AcknowledgeAfterFailoverTest. These tests were globally excluded (Excludes file). New tests FBT.testClientAcknowledgedSessionCloseAfterFailover/testTransactedSessionCloseAfterFailover/testAcknowledgeAfterFailoverForAsynchronousConsumer cover these scenarios.
3) MessageDisappearWithIOExceptionTest. Tests were added after a defect arising from Java Broker use of MINA. Test scenario covered by FBT.testRecoverAfterFailoverInAutoAcknowledgeMode.
4) 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.
5) QuickAcking. Test exercised same code paths as FBT.testMessageProducingAndRollbackAfterFailover.
CloseAfterConnectionFailureTest duplicates FailoverMethodTest#testNoFailover. The testcase was actually excluded from all profiles.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1224788 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/client/src/test')
0 files changed, 0 insertions, 0 deletions