Websocket: move protocol tests to the new TestMessagingProtocol class

Bug #1538895 reported by Eva Balycheva on 2016-01-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eva Balycheva

Bug Description

When we test our websocket transport, we test two types of things:
1. Our websocket API
2. Our websocket driver, factories, protocols

I think 'MessagesBaseTest' should contain only websocket API tests, but I see now that it contains also protocol-related tests, for example, 'test_invalid_request':
See https://github.com/openstack/zaqar/blob/master/zaqar/tests/unit/transport/websocket/v2/test_messages.py#L596

This test case (and maybe some others) can be put in the newly introduced 'TestMessagingProtocol' class:
See https://github.com/openstack/zaqar/blob/master/zaqar/tests/unit/transport/websocket/test_protocol.py

Eva Balycheva (ubershy) on 2016-01-28
Changed in zaqar:
assignee: nobody → Eva Balycheva (ubershy)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers