Websocket: move protocol tests to the new TestMessagingProtocol class

Bug #1538895 reported by Eva Balycheva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
New
Undecided
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)
Changed in zaqar:
assignee: nobody → Eva Balycheva (ubershy)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.