The websocket requires a set of basic unit tests to verify it's functionality and that there are no serious issues with the presently implemented feature set.
I would suggest the following tests be implemented at this time:
Basic Connection
On connection write
On read write
SSL test
More over as the functionality of the websocket evolves to meet the needs of the QuoteService classes these tests aught to be revised and expanded upon so that they reflect it's new state and functionality.
Implementation
The basic framework for testing the websocket already exist, the unit tests need only be written.
There is one additional challenge in that we will be required to spin up a python tests server to run during the unit tests and supply the appropriate responses to the client , this will necessitate some cmake magic I fear.
Overview
The websocket requires a set of basic unit tests to verify it's functionality and that there are no serious issues with the presently implemented feature set. I would suggest the following tests be implemented at this time:
More over as the functionality of the websocket evolves to meet the needs of the QuoteService classes these tests aught to be revised and expanded upon so that they reflect it's new state and functionality.
Implementation
The basic framework for testing the websocket already exist, the unit tests need only be written.
There is one additional challenge in that we will be required to spin up a python tests server to run during the unit tests and supply the appropriate responses to the client , this will necessitate some cmake magic I fear.