|about 16 hours ago||1 day ago|
|MIT License||MIT License|
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.
Writing tests for a Kubernetes Operator
3 projects | dev.to | 7 Oct 2023
Gomega: is a test assertion library, a vital dependency on Ginkgo.
Learning Go by examples: part 6 - Create a gRPC app in Go
7 projects | dev.to | 18 Aug 2021
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
2 projects | news.ycombinator.com | 16 Jun 2021
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
7 projects | /r/golang | 28 Mar 2021
Go generics beyond the playground
6 projects | dev.to | 25 Mar 2021
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's your favourite part of unit testing?
2 projects | /r/golang | 19 Jan 2023
I also use BDD (Gherkin with godog in particular) to verify and document the expected behaviour of a product from an end user's perspective when needed. I usually do this when the product also contains untested code that I have no control over when I'm working on a problem - this gives me peace of mind over something I can't control while doubling as documentation.
Behaviour Driven Development (BDD) boilerplate tests generator
3 projects | /r/golang | 20 Mar 2022
It looks like it is not possible to share steps between scenario's or features. In https://github.com/cucumber/godog it is possible to share steps.
Behaviour Driven Development (BDD) boilerplate tests generator for Golang
2 projects | /r/golang | 21 Jan 2022
Differences between gherkingen and godog are:
BDD (Behavior-driven development) mit Go
2 projects | dev.to | 18 May 2021
What are some alternatives?
ginkgo - A Modern Testing Framework for Go
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.
venom - 🐍 Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
Gauge - Light weight cross-platform test automation
goblin - Minimal and Beautiful Go testing framework
go-vcr - Record and replay your HTTP interactions for fast, deterministic and accurate tests