I don't understand popularity of a table driven tests approach

This page summarizes the projects mentioned and recommended in the original post on /r/golang

Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Revelo Payroll - Free Global Payroll designed for tech teams
  • Onboard AI - Learn any GitHub repo in 59 seconds
  • Testify

    A toolkit with common assertions and mocks that plays nicely with the standard library

    Golang provide basic building blocks, which are sufficient to run tests. You can use third party libraries like https://github.com/stretchr/testify , but they are not in a standard for good reason: they heavily use reflections, which is not an idiomatic approach. And thanks to that you can swap them as you want

  • go-strftime

    strftime/strptime for Go

    Yeah. Try getting 100% code and branch coverage in something like [this](https://github.com/ncruces/go-strftime/blob/main/strftime_test.go] without tables.

  • SonarLint

    Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts