Releases: gridsmartercities/pywsitest
Release v0.3.8
0.3.8 (2021-11-03)
Websocket headers, top level lists, first draft of rest requests
Users can now use headers when connecting to websocket hosts - headers can be used for auth.
Responses where the top level is a list can now be correctly parsed and handled.
First draft of sending rest requests as part of a WSTest now for flows that use both websockets and rest requests in tandem. Written with the help of @Maxoyd 👍
Received response logging
When the test times-out waiting for a response; users can now enable automatic logging of any received responses alongside the default logging of responses the test runner was still waiting for.
Response list testing
Users can now test that the n-th element of a list matches a value, or that at least one element in a list matches a value.
Users can also resolve the n-th element of a list in a response for a message payload too.
Better response testing
Users can now better test attributes in websocket responses.
Message send delays
Users can delay the sending of messages and triggered messages to be sent to a websocket host.
Bug fixed where an error was thrown if a user was connecting to an unsecure server (ws:// rather than wss://).
Response data extraction and better error handling
Users can extract data from responses to use in triggered messages to be sent to a websocket host.
Exceptions from failed tests give details about which responses haven't been received or which message failed to send.
Whitespace and newlines are automatically removed from urls and query parameters.
First public release
Users can create a test runner that connects to a url with http query parameters.
The test runner can send configured messages to the websocket host, and can receive messages and assert that specific messages have been received.
Users can also trigger messages to be sent when certain messages are received.
Users can assert that the runner has successfully finished sending and receiving messages.
Users can configure timeouts for sending messages, receiving messages, and the overall test execution.