testcase
gomega
Our great sponsors
testcase | gomega | |
---|---|---|
14 | 6 | |
116 | 2,072 | |
- | - | |
6.6 | 8.2 | |
8 days ago | 20 days ago | |
Go | Go | |
Apache License 2.0 | 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.
testcase
- Updates to `testcase` Testing Framework: Enhanced Assertions, Time Manipulation, Random Value Generation and More!
-
testing utility for time manipulation and pretty printing
One of them focuses on time manipulation for testing purposes: - Freeze time to a specific point. - Travel back to a specific time, but allow time to continue moving forward. - Scale time by a given scaling factor will cause the time to move at an accelerated pace. - No dependencies other than the stdlib - Nested calls to timecop.Travel is supported - Works with any regular Go projects
-
fault injection utilities and HTTP middleware contracts are now available in the testcase package
Fault Inject Package Repo URL
-
Read/Write FileSystem header interface for dependency injection
If you like test-driven design, check out my testing framework. https://pkg.go.dev/github.com/adamluzsi/testcase https://github.com/adamluzsi/testcase
- add support for IsEqual function based equality assertion in `testcase/assert.Asserter`
-
The Big List of Naughty Strings is incorporated into the testcase's random generator. (v0.71.0)
refs: - https://github.com/adamluzsi/testcase/releases/tag/v0.71.0 - https://github.com/minimaxir/big-list-of-naughty-strings
- testcase testing framework is finally dependency-free
-
(: yet another assertion library, this time in the testcase testing framework
In the testcase testing framework, I mostly used github.com/stretchr/testify for the assertions, and everywhere where I work with the testing framework. Most of the time, I barely use the full potential of testify, just some basic assertations like Contains and Equal. I decided to ship these basic assertions within the testing framework, so when I don't need heavy lifting with a full-fledged assertion library, I don't need to import one.
- Random values for testing, providing testing seed make it idempotent as well.
- Support is added for BeforeAll/AfterAll/AroundAll hooks in the testcase testing framework
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?
frisby - API testing framework inspired by frisby-js
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
GoAws - AWS (SQS/SNS) Clone for Development testing
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
goc - A Comprehensive Coverage Testing System for The Go Programming Language
godog - Cucumber for golang
assert - :exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions
gnomock - Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻
goblin - Minimal and Beautiful Go testing framework
is - Professional lightweight testing mini-framework for Go.
gocheck - Rich testing for the Go language