Boosting test coverage for microservices

Good enough test coverage enables truly continuous deployment. Unit tests get one so far, but integration tests with actual counterparties make more sense for some features. Measuring and monitoring the code coverage for the integration tests helps to achieve the ideal deployment pipeline.

Golab #1
60 min
November 20th, 2023


Unit tests are the bread and butter of any project's quality assurance process. There is tooling that helps us find untested areas, records the coverage percentages, and notifies us if the changes cause a drop in the test scope. However, sometimes more than unit tests are needed. Running the executable in a test setup that resembles its actual use case without unit testing tooling is, in some cases, a more appropriate way to verify correct functionality.

Go 1.20 introduced the instrumentation of the application binary and enabled collecting code coverage for the integration tests. The new feature inspired the Findy Agency team to refactor their integration testing pipeline for their microservices. Along with the updated Go-toolchain, the new solution relies on GitHub Actions, Docker, and GitHub Packages. It enables the team to monitor the test coverage and quality better and share the test scripts effectively between different services.

Stay connected

You can subscribe to our newsletter to stay updated on the latest news and announcements. Follow us on social media to join our community and engage with other attendees, speakers, and staff. We're on Twitter, Mastodon, Youtube and Facebook. Don't forget to use our official hashtag #GoLab2023 to share your experience and connect with other attendees on social media.

Subscribe to our newsletter

We hate spam just as much as you do, which is why we promise to only send you relevant communications. We respect your privacy and will never share your information with third parties.
©2023 GoLab | The international conference on Go in Florence-Design & devCantiere Creativo-Made withDatoCMS