revali_test 0.1.0
revali_test: ^0.1.0 copied to clipboard
Test helpers for Revali servers — drive a generated server in-process, without binding a socket
CHANGELOG #
0.1.0 | 08.13.26 #
Features #
TestHeaders.addappends instead of overwriting, matchingdart:io. A response setting several cookies — each needing its ownSet-Cookieline — arrived with only the last one, so tests could not see the rest.TestRequestsends binary and streamed bodies as they are. Previously anything that was not aStringwasjsonEncoded, so aList<int>upload arrived as the text"[1,2,3]", and aStreambody was read as WebSocket frames rather than a request body — leaving the request empty. WebSocket input now arrives through its ownwebSocketInputparameter, so a streamed HTTP body is expressible at all.- First release.
revali_testwas previouslypublish_to: none, so the testing helpers the docs and the internal suite rely on were unavailable to anyone outside this repo. It exposesTestServer, which stands in for anHttpServerso a generated server runs in-process without binding a socket, plusTestRequest/TestResponse/TestHeadersand theexpectRecentHttpDatematcher.
1.0.0 | 08.12.26 #
Features #
- First release.
revali_testwas previouslypublish_to: none, so the testing helpers the docs and the internal suite rely on were unavailable to anyone outside this repo. It exposesTestServer, which stands in for anHttpServerso a generated server runs in-process without binding a socket, plusTestRequest/TestResponse/TestHeadersand theexpectRecentHttpDatematcher.