dbcleaner
gomega
Our great sponsors
| dbcleaner | gomega | |
|---|---|---|
| 1 | 6 | |
| 157 | 2,072 | |
| - | - | |
| 1.8 | 8.2 | |
| over 2 years ago | 15 days ago | |
| Go | Go | |
| 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.
dbcleaner
-
The Big Unit Test Misunderstanding
It is not hard to isolate and stub a database the problem is you will not catch a lot of errors, e.g. writing a 40 char string into a VCHAR(10), DateTime conversations, ...
In Ruby on Rails it is quite common to use a real database in the unit tests. Even before containers came out and it is still fast (yes, less than 1 second).
In rails you use the same database instance for all the tests, so you do not have spin up a database instance for every case. Instead you use a database cleaner.
There also exists a JS implementation: https://github.com/khaiql/dbcleaner
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?
go-carpet - Tool for show test coverage in terminal for Go source files
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
bro - bro watch files in directory and run tests for them
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
Gauge - Light weight cross-platform test automation
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
goblin - Minimal and Beautiful Go testing framework
godog - Cucumber for golang
testfixtures - Ruby on Rails like test fixtures for Go. Write tests against a real database
goc - A Comprehensive Coverage Testing System for The Go Programming Language
gocheck - Rich testing for the Go language