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.
ginkgo
-
Mastering Golang Debugging in Emacs
Debug both standard applications and Ginkgo tests (this is what I'm using at the moment đ€·)
-
Go-DOM - 1st major milestone
Let's explore a simple test, as it looks now in the code base (the code uses Ginkgo and Gomega, a somewhat overlooked combination IMHO)
-
Functional Programming in Go
Take a look at the Ginkgo testing framework to see the horrors of shoe horning FP into Go
https://onsi.github.io/ginkgo/#writing-specs
-
Show HN: Gomponents, HTML components in pure Go
It's the same with the Ginkgo testing library: "After the package books_test declaration we import the ginkgo and gomega packages into the test's top-level namespace by performing a . dot-import. Since Ginkgo and Gomega are DSLs this makes the tests more natural to read."
https://onsi.github.io/ginkgo/
-
Leverage Your Test Suite With testcontainers-go & docker-compose
The ginkgo testing framework helps us in building the test suite. It's entirely written in Go. Furthermore, it provides a CLI utility to set up and run the tests. Since we will use it later, let's download it from here. You can download it in two ways:
-
Writing tests for a Kubernetes Operator
Ginkgo: a testing framework based on the concept of â"Behavior Driven Development" (BDD)
-
We moved our Cloud operations to a Kubernetes Operator
We were also able to leverage Ginkgo's parallel testing runtime to run our integration tests on multiple concurrent processes. This provided multiple benefits: we could run our entire integration test suite in under 10 minutes and also reuse the same suite to load test the operator in a production-like environment. Using these tests, we were able to identify hot spots in the code that needed further optimization and experimented with ways to save API calls to ease the load on our own Kubernetes API server while also staying under various AWS rate limits. It was only after running these tests over and over again that I felt confident enough to deploy the operator to our dev and prod clusters.
-
Recommendations for Learning Test-Driven Development (TDD) in Go?
A bit off-topic, but i really like the ginkgo BDD framework
-
Start test names with âshouldâ (2020)
You obviously are not familiar with the third circle of golang continuous integration hell that is ginkgo+gomega:
https://onsi.github.io/ginkgo/#adding-specs-to-a-suite
Itâs actually worse than that example suggests. Stuff like Expect(âtype safetyâ).ShouldBe(GreaterThan(13)) throws runtime errors.
The semantics of parallel test runs werenât defined anywhere the last time I checked.
Anyway, youâll be thinking back fondly to the days of TestShouldReplaceChildrenWhenUpdatingInstance because now you need to write nested function calls like:
Context(âinstancesâ, func âŠ)
Describe(âthat are being updatedâ, âŠ)
Expect(âshould replace childrenâ, âŠ)
And to invoke that from the command line, you need to write a regex against whatever undocumented and unprinted string it internally concatenates together to uniquely describe the test.
Also, they dump color codes to stdout without checking that they are writing to a terminal, so there will be line noise all over whatever automated test logs you produce, or if you pipe stdout to a file.
-
ginkgo integration with jira/elasticsearch/webex/slack
If you are using Ginkgo for your e2e, this library might of help.
godog
-
Quitting early for the win!
Quick side note - this is probably the subject of a whole other blog post but my current favourite way of testing CLI tools uses godog to write tests. It can be a little complex but I've found it supremely powerful. Here are some good examples of how I've approached it with layli and wait-for.
- Integration Tests in Go with Cucumber, Testcontainers, and HTTPMock
- O que Ă© BDD e quando vocĂȘ deve considerar
-
Godog integration test failing with weird error
It's complaining about a file missing in $GOPATH/pkg... but I'm not sure how do I get the packages its asking for. Things I have tried: - running go mod tidy - running go get -u github.com/cucumber/godog (hoping it would add the files to pkg/mod/... - Uninstalled and installed Go again.
-
What's your favourite part of unit testing?
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
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
Differences between gherkingen and godog are:
- BDD (Behavior-driven development) mit Go
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.
httpexpect - End-to-end HTTP and REST API testing for Go.
Gauge - Light weight cross-platform test automation
goblin - Minimal and Beautiful Go testing framework
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
gomega - Ginkgo's Preferred Matcher Library
gocheck - Rich testing for the Go language
venom - đ Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions