-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unit tests for StreamPeer
and StreamPeerBuffer
#95784
Add unit tests for StreamPeer
and StreamPeerBuffer
#95784
Conversation
StreamPeer::get_string
and StreamPeer::get_utf8_string
bug (#95783)StreamPeer::get_string
and StreamPeer::get_utf8_string
bug
Because the discussion around if the bug referenced by this PR is a bug or not, I can extract all the other unit test in another PR to get that one move faster and get merged. Thoughts? |
StreamPeer::get_string
and StreamPeer::get_utf8_string
bugStreamPeer
and StreamPeerBuffer
I decided to remove #95783 fix and keep this PR as only adding tests |
@timothyqiu Could you please remove |
@Calinou Can I get a review now that the PR is only adding Unit Tests? |
You should use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be honest, I wasn't sure about the separation of the StreamPeer and StreemPeerBuffer tests, but after looking into this a bit longer I now think it makes sense. Maybe adding a StreamPeerDummy/Mock would be the most correct way to test them apart, but I'd leave it up to you if you want to do that.
Either way, needs to be squashed into one commit.
6262e71
to
adab6da
Compare
In order to add a mock I prefer to wait until a definition on #95224 where I added a Mocking library. If I get that PR merged with the mocking library I will be glad to revisit this tests and use a mock. |
adab6da
to
ff10dee
Compare
Thanks! |
This PR aims to help "fix" #43440
Adding unit tests for
StreamPeer
andStreamPeerBuffer