-
-
Notifications
You must be signed in to change notification settings - Fork 94
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 implementation of interfaces project #131
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for cyf-systems ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
"github.com/stretchr/testify/require" | ||
) | ||
|
||
func TestInitialBytesAreRead(t *testing.T) { |
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.
could be done as a table driven test, which is better go idiom imo
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.
Could I bother you to sketch out what the per-testcase struct would look like here?
I put together my best guess in buffer_table_test.go
, but it feels like quite a bit of added complexity, and like it makes the tests harder to read and interpret. Maybe I'm just not looking at it the right way, and that's not what you had in mind?
Also switch FilteringPipe tests to be table-driven.
cc9349f
to
64cf92e
Compare
Sample answer for the interfaces project in #130