Golang testing: Difference between revisions
From wikinotes
No edit summary |
No edit summary |
||
Line 68: | Line 68: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
</blockquote><!-- Assertions --> | </blockquote><!-- Assertions --> | ||
= Benchmarking = | |||
<blockquote> | |||
There are tools for benchmarking. See docs | |||
</blockquote><!-- Benchmarking --> | |||
= Fuzzing = | |||
<blockquote> | |||
There are tools for fuzzing tests. See docs | |||
</blockquote><!-- Fuzzing --> |
Revision as of 21:54, 6 June 2022
Go ships with a test suite.
Documentation
testing
https://pkg.go.dev/testing@go1.18.3
Usage
go test -run # run all tests go test -run Foo # run top-level tests containing 'Foo'
Example
The builtin go test framework is fairly minimalist.
Tests are just functions, you can loop them if useful.
Tests are typically kept alongside code.
// myproject/mypackage/mylib.go package mypackage func Hello(name string) string { return "Hello, " + name }// myproject/mypackage/mylib_test.go package mypackage import "testing" func TestHello(t *testing.T) { res := Hello("Adam") if res != "Hello, Adam" { t.Errorf("Hello() result did not match") } }
Assertions
There are no assertions, you are responsible for tests and messages.
func TestHello(t *testing.T) { // log message and fail (but continue executing) t.Errorf("An expectation was not satisfied") t.Fail() // mark test as failed, but continue t.FailNow() // mark test as failed and stop executing t.Skip("Reason") // log, and stop executing t.TempDir() // provides a tempdir that is deleted once test finishes running }
Benchmarking
There are tools for benchmarking. See docs
Fuzzing
There are tools for fuzzing tests. See docs