expect
A simple assertion library that you probably shouldn't use. (by pkg)
subtest
A utility for generating runnable sub-tests in Go (by clarify)
| expect | subtest | |
|---|---|---|
| 1 | 1 | |
| 132 | 6 | |
| 0.8% | - | |
| 0.0 | 0.0 | |
| over 4 years ago | about 1 year ago | |
| Go | Go | |
| BSD 2-clause "Simplified" License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
expect
Posts with mentions or reviews of expect.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-25.
-
Go generics beyond the playground
We have to pass in the t parameter. It's a minor inconvenience, but enough for Dave Cheney to write a quite interesting package for solving it. Not recommended for production use, I might add.
subtest
Posts with mentions or reviews of subtest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-25.
-
Go generics beyond the playground
Starting out with Go generics, in order to do something useful, we need a problem to solve. The problem I have picked for this article is one that I have tried to solve before when designing the test matcher/assertion library that we use to test the Clarify back-end at Searis. But first, you probably have a question: with all the great test matcher libraries we have in Go, why on earth would we want to write a new one? To answer that, it's worth having a closer look at at one of the existing matcher libraries. Does it solve it's mission in a useful way, and with the best possible package design?
What are some alternatives?
When comparing expect and subtest you can also consider the following projects:
go - The Go programming language
gomega - Ginkgo's Preferred Matcher Library
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
learn-go-with-tests - Learn Go with test-driven development