verify
gomega
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.
verify
-
fluentassert/verify 1.0.0 is released
After more than 4 months of RC phase, I published a stable release of https://github.com/fluentassert/verify
-
fluentassert - asking for feedback
I am the author of https://github.com/fluentassert/verify and I am looking for feedback :)
-
Any major projects using generics?
https://github.com/fluentassert/verify another assertion library
- fluentassert - an extensible assertion library
-
fluentassert - a prototype of yet another assertion library
Today morning I woke up with an idea to create an assertion library with a more user-friendly and extensible API (than other popular libraries). The main idea is to create a more user-friendly API than other libraries. Here is the prototype: https://github.com/pellared/fluentassert
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.
What are some alternatives?
is - Professional lightweight testing mini-framework for Go.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
assertions - Fluent assertion-style functions used by goconvey and gunit. Can also be used in any test or application.
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
btree - BTree provides a simple, ordered, in-memory data structure for Go programs.
godog - Cucumber for golang
gocrest - GoCrest - Hamcrest-like matchers for Go
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
testcase - testcase is an opinionated testing framework to support test driven design.
goblin - Minimal and Beautiful Go testing framework
dsunit - Datastore Testibility
gocheck - Rich testing for the Go language