gomega
GoConvey
Our great sponsors
gomega | GoConvey | |
---|---|---|
6 | 3 | |
2,072 | 8,093 | |
- | 0.6% | |
8.2 | 5.4 | |
19 days ago | 11 days ago | |
Go | Go | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gomega
-
Writing tests for a Kubernetes Operator
Gomega: is a test assertion library, a vital dependency on Ginkgo.
- Quick tip: Easy test assertions with Go generics
-
Learning Go by examples: part 6 - Create a gRPC app in Go
Gomega is a Go library that allows you to make assertions. In our example, we check if what we got is null, not null, or equal to an exact value, but the gomega library is much richer than that.
-
Tips to prevent adoption of your API
Depends on the API and how much testing you need. You want to test your code, not the API's availability or correctness.
But it can be as easy as using a fake http library and mocking the responses, or using a httptest server: https://onsi.github.io/gomega/#ghttp-testing-http-clients
If the API is complicated and you have to write your own fake server, that might not make sense for small projects.
- fluentassert - a prototype of yet another assertion library
-
Go generics beyond the playground
If we do the count, we gather that subtest appear to solve five out of the six problems we identified with the assert library. At this point though, it's important to note that at the time when the assert package was designed, the sub-test feature in Go did not yet exist. Therefore it would have been impossible for that library to embed it into it's design. This is also true for when Gomega and Ginko where designed. If these test frameworks where created now, then most likely some parts of their design would have been done differently. What I am trying to say is that with even the slightest change in the Go language and standard library, completely new ways of designing programs become possible. Especially for new packages without any legacy use-cases to consider. And this brings us to generics.
GoConvey
-
Gokiburi: Automatic Test Runs for Go Projects
I have always liked to use the similar GoConvey tool for automatic test runs during development, but it has definitely started to “show its age” and since Go 1.20 it hasn’t been able to parse code coverage correctly. So, I decided to dive into making my own tool to replace it for me.
-
Is there a more detailed test coverage report than go test -cover?
IIRC you can use http://goconvey.co/ just for the reports
-
Do you prefer go-convey over golang's t.Run?
For a generic usecase, do you see Go-convey adding any benefit over simple golang t.Run?
What are some alternatives?
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
ginkgo - A Modern Testing Framework for Go
godog - Cucumber for golang
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
goblin - Minimal and Beautiful Go testing framework
gocheck - Rich testing for the Go language
Gauge - Light weight cross-platform test automation
GoAws - AWS (SQS/SNS) Clone for Development testing