-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace testing framework (go-check) with standard library assertions #15
Milestone
Comments
Closed
theckman
added a commit
that referenced
this issue
Jul 16, 2018
In preparation for executing on #15 (already opened in #17) we need to disable testing against older versions of the Go toolchain. There are a few reasons for this, the largest being they don't support subtests. These versions, including Go 1.7 and 1.8, are EOL by the Go authors so there's also lack of upstream support for these toolchains. This was discussed a bit in #18 and on [Slack](https://gophers.slack.com/archives/CBP4N9BEU/p1531704009000014). Fixes #18 Signed-off-by: Tim Heckman <t@heckman.io>
theckman
added a commit
that referenced
this issue
Jul 16, 2018
In preparation for executing on #15 (already opened in #17) we need to disable testing against older versions of the Go toolchain. There are a few reasons for this, the largest being they don't support subtests. These versions, including Go 1.7 and 1.8, are EOL by the Go authors so there's also lack of upstream support for these toolchains. This was discussed a bit in #18 and on [Slack](https://gophers.slack.com/archives/CBP4N9BEU/p1531704009000014). Fixes #18 Signed-off-by: Tim Heckman <t@heckman.io>
theckman
added a commit
that referenced
this issue
Jul 16, 2018
In preparation for executing on #15 (already opened in #17) we need to disable testing against older versions of the Go toolchain. There are a few reasons for this, the largest being they don't support subtests. These versions, including Go 1.7 and 1.8, are EOL by the Go authors so there's also lack of upstream support for these toolchains. This was discussed a bit in #18 and on [Slack](https://gophers.slack.com/archives/CBP4N9BEU/p1531704009000014). Fixes #18 Signed-off-by: Tim Heckman <t@heckman.io>
theckman
added a commit
that referenced
this issue
Jul 16, 2018
In preparation for executing on #15 (already opened in #17) we need to disable testing against older versions of the Go toolchain. There are a few reasons for this, the largest being they don't support subtests. These versions, including Go 1.7 and 1.8, are EOL by the Go authors so there's also lack of upstream support for these toolchains. This was discussed a bit in #18 and on [Slack](https://gophers.slack.com/archives/CBP4N9BEU/p1531704009000014). Fixes #18 Signed-off-by: Tim Heckman <t@heckman.io>
theckman
added a commit
that referenced
this issue
Jul 16, 2018
In preparation for executing on #15 (already opened in #17) we need to disable testing against older versions of the Go toolchain. There are a few reasons for this, the largest being they don't support subtests. These versions, including Go 1.7 and 1.8, are EOL by the Go authors so there's also lack of upstream support for these toolchains. This was discussed a bit in #18 and on [Slack](https://gophers.slack.com/archives/CBP4N9BEU/p1531704009000014). Fixes #18 Signed-off-by: Tim Heckman <t@heckman.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While overall there's nothing wrong with the
go-check
package, as least from my perspective as a user, it does add some overhead in to learning how to contribute unit tests to this package. We should look at replacing the go-check assertions with table-driven tests using thetesting
package from the stdlib.(This is already a WIP)
The text was updated successfully, but these errors were encountered: