summaryrefslogtreecommitdiffstats
path: root/tests/unit/rpc/test_qpid.py
diff options
context:
space:
mode:
Diffstat (limited to 'tests/unit/rpc/test_qpid.py')
-rw-r--r--tests/unit/rpc/test_qpid.py12
1 files changed, 6 insertions, 6 deletions
diff --git a/tests/unit/rpc/test_qpid.py b/tests/unit/rpc/test_qpid.py
index 02e8e20..42a6e6b 100644
--- a/tests/unit/rpc/test_qpid.py
+++ b/tests/unit/rpc/test_qpid.py
@@ -45,8 +45,7 @@ FLAGS = cfg.CONF
class RpcQpidTestCase(utils.BaseTestCase):
- """
- Exercise the public API of impl_qpid utilizing mox.
+ """Exercise the public API of impl_qpid utilizing mox.
This set of tests utilizes mox to replace the Qpid objects and ensures
that the right operations happen on them when the various public rpc API
@@ -479,10 +478,11 @@ class RpcQpidTestCase(utils.BaseTestCase):
impl_qpid.Connection.pool.get()
def test_call_with_timeout(self):
- """A little more indepth for a timeout test. Specifically we are
- looking to simulate the event sent to qpid dying on the vine due
- to a TTL. A string test that actually involved qpid would be
- excellent, but this at least verifies that the exceptions flow
+ """A little more indepth for a timeout test.
+
+ Specifically we are looking to simulate the event sent to qpid dying
+ on the vine due to a TTL. A string test that actually involved qpid
+ would be excellent, but this at least verifies that the exceptions flow
like they should. TODO(beagles): is this really necessary or is
the the case for qpid at least the basic timeout test is
sufficient.