gomega
is
Our great sponsors
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.
is
- The Go libraries that never failed us: 22 libraries you need to know
-
is there a way to write test in a sane way?
I use https://github.com/matryer/is which is a simplified version of testify.
-
Testing frameworks, which to use?
testify off steroids, all you ever need: is
-
What are the REST API reference projects that can be used as a guide in 2021?
However your point is valid. Check matryer/is for unit test writing. DATA-DOG/go-sqlmock to test database interactions.
-
Beginner here, I'm wondering how ok it is to omit err return values as I am trying to approach things from test-driven perspective
Even better, use https://github.com/matryer/is.
-
"is" testing framework?
Probably they talking about https://github.com/matryer/is ?
- fluentassert - a prototype of yet another assertion library
What are some alternatives?
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
verify - Extensible, type-safe, fluent assertion Go library.
godog - Cucumber for golang
GoAws - AWS (SQS/SNS) Clone for Development testing
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
gnomock - Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻
goblin - Minimal and Beautiful Go testing framework
gotest.tools - A collection of packages to augment the go testing package and support common patterns.
gocheck - Rich testing for the Go language