gomega

I've seen things like: go-supertest - https://github.com/franela/go-supertest and gomega - https://github.com/onsi/gomega And while appealing in some ways, I always end up at the same place: In many instances these tools seem to go against the principles of idiomatic go. I realize I could be totally wrong, and I also see how being diligent about state is theoretically useful for efficiently identifying/exposing points of failure. but many of the go unit-tests I end up writing take a fair amount of effort for setting up the proper state. And then everything else is pretty much a 1-3 liner to check for failures. If you look at http://onsi.github.io/ginkgo/, I think you'll see what I mean. It's shoe-horned in there. SO, what do you all do that you think is amazingly awesome or at least best-practices beyond golang.org recommendations to co