Interfaces in Go - Discovering Behavior

[@Cspartan_1291]

MOM! Wake up! Matthew uploaded a new video!

[@sudomateo]

This is the way!

[@sudomateo]

Please excuse the nasally voice. I recorded this just as I was getting sick so I was a bit stuffy.

[@selvamp5775]

👏👏👏

[@aniellosgambato]

I like this content. Just one thing I know this is a jus a simple example but you are not testing the SendNotification function at all here. I see that you want show how you can take benefit of interfaces to create mocks that can help during unit tests, but this is a little bit misleading on how write a good unit test. By the way I appreciate your efforts and I am waiting for other content related to Golang. B.R.

[@sudomateo]

Thank you! More content will be coming soon. I wasn't going to include any testing in this video at first but the I was like ah heck why not? I really wanted to show how one can implement interfaces to be used in tests rather than writing a perfect unit test. I probably should have asserted on the message to test the behavior specific to SendNotification. In the current form it's really just testing that the notifier(s) get called.

[@indifferentghozt]

Don't forget to hit that bell!

[@sudomateo]

Like. Subscribe. Hit the bell. Grow the beard. All the good things!

[@0lange]

Loving the go content, so clear and easy to grasp. I would pay for your courses 😆

[@sudomateo]

Thank you for the kind words! I'm not against creating course content, I would just need to dedicate time to creating the content and make sure it's financially accessible to everyone. I have some strong opinions on some of the course content out there that takes advantage of aspiring engineers.

[@0lange]

Fair enough :I) Also a future video suggestion: concurrency stuff (channel and mutex)

[@sudomateo]

@@0lange I got you! Concurrency stuff is next on the list. I ranked some suggestions based on frequency and concurrency was top 3. I'll be recording that when I'm back from GopherCon.