Testify VS ginkgo

FWIW, I've been using testify and mockery for years.

To answer OP directly, I am largely quite happy with mockery (and testify) to write expressive tests.

Como herramientas te recomiendo: FastJson https://github.com/valyala/fastjson : Si necesitas leer jsons Testify https://github.com/stretchr/testify : Para mockear y testear

Indispensable for testing your code: https://github.com/stretchr/testify

Best tool in the ecosystem testify. Learn about Table driven test, suite - saves your time so much with setup & teardown. Absolutely one thing you need to follow, if you see anything breaking (or bugs) add tests for that, could be unit tests or integration tests, this's of huge value and reduces manual testsing.

I use https://github.com/stretchr/testify in tests, it prints structs and diffs very well

Assertion libraries that people seem to love: - testify (my favorite) - go-cmp is a more barebones library - gotest.tools -- I have never used this but some swear by it

It can be easily used with https://pkg.go.dev/flag or https://github.com/spf13/viper (for configuration) and even https://github.com/stretchr/testify (for asserting)

If you are using Ginkgo for your e2e, this library might of help.

https://onsi.github.io/ginkgo/ offers a simple way to create tables with different scenarios useful to generate different test cases based on a file like a yml without to need to develop useless code. Maybe at start seems to be a little verbose but depends how you design the test case.

If you like BDD and more expressive tests, go get ginkgo. It is a pain in the back get the hang of its R-spec like syntax, but if you're good at it and you like it, it is very expressive and readable. It has its own matcher (assertions library), gomega, but if you don't like it, you can still use testify instead.

What are people’s thoughts on testing frameworks? I’ve heard that most devs only use the testing package in the standard library and the testify package for assertions— I assume this is because Go is meant to be lightweight and scalable, and adding external dependencies basically goes against that. But I’ve also seen devs use packages like ginkgo to make tests more structured and readable. What do you guys think?

Ginkgo Behavioural test framework

If you write your tests with Ginkgo [0] its CLI can do this for you. It also has nice facilities to quickly disable a test or portion of a test by pretending an X to the test function name, or to focus a test (only run that test) by prepending an F. It’s pretty nice.

[0]: https://onsi.github.io/ginkgo/

The BDD testing framework Ginko [1] has some "weird" / unidiomatic patterns, yet it is very popular

https://github.com/onsi/ginkgo

To settle an argument amongst my coworkers, I started a Twitter poll on using Gingko for golang unit testing. Some like the framework because it makes tests clean. Others hate it with a firey passion.

As a big fan of automated testing, it’s comforting to learn that we can easily write tests for our controllers using envtest (which runs a local k8s control plane so we can run our tests against it), the Gingko testing framework and the Gomega matching/assertion library: