|3 months ago||12 days ago|
|GNU General Public License v3.0 or later||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.
What are you using for testing your IAC?
3 projects | reddit.com/r/devops | 1 Dec 2021
Terraform providers are tested this way (separate cloud account w/ create/destroy) paired with VCR to record and replay the HTTP requests.
Go Package for testing HTTP interactions: github.com/dnaeon/go-vcr
2 projects | dev.to | 8 May 2021
Let me introduce to you github.com/dnaeon/go-vcr.
best way to mock/unit test http.Client?
4 projects | reddit.com/r/golang | 15 Mar 2021
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 | reddit.com/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 are some alternatives?
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
godog - Cucumber for golang
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
goblin - Minimal and Beautiful Go testing framework
testfixtures - Ruby on Rails like test fixtures for Go. Write tests against a real database
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
frisby - API testing framework inspired by frisby-js
go-mutesting - Mutation testing for Go source code
Gauge - Light weight cross-platform test automation
ginkgo - A Modern Testing Framework for Go
bro - bro watch files in directory and run tests for them
gofight - Testing API Handler written in Golang.