Trials and tribulations of testing in Go (Go Time #174)

Changelog Master Feed

Testing can be hard, how to test, where to test, what is a good test? All questions that can be deceptively difficult to answer. In this episode we talk about the trials and tribulations of testing and why it can be argued to be especially difficult in Go.

Leave us a comment

Changelog++ members save 5 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Teleport – Quickly access any resource anywhere using a Unified Access Plane that consolidates access controls and auditing across all environments - infrastructure, applications, and data. Try Teleport today in the cloud, self-hosted, or open source at goteleport.com
• LaunchDarkly – Ship fast. Rest easy. Deploy code at any time, even if a feature isn’t ready to be released to your users. Wrap code in feature flags to get the safety to test new features and infrastructure in prod without impacting the wrong end users.
• Sourcegraph – Sourcegraph is universal code search for every developer and team. Easily search across all the code that matters to you and your organization: find example code, explore and read code, debug issues, and more. Head to info.sourcegraph.com/changelog and click the button “Try Sourcegraph now” to get started.

Featuring:

• Jon Sabados – Twitter, GitHub, Website
• Angelica Hill – Twitter, GitHub, LinkedIn
• Kris Brandow – Twitter, GitHub
• Mat Ryer – Twitter, GitHub, LinkedIn, Website

Show Notes:

• dig - a reflection based dependency injection toolkit for Go
• is - Mat Ryer’s lightweight testing mini-framework for Go
• testing - from the Standard Library
• Learn Go with Tests

Something missing or broken? PRs welcome!