Package clock provides an abstraction for system time that enables testing of time-sensitive code.

Package oglematchers provides a set of matchers useful in a testing or mocking framework. These matchers are inspired by and mostly compatible with Google Test for C++ and Google JS Test.

Package ogletest provides a framework for writing expressive unit tests. It integrates with the builtin testing package, so it works with the gotest command. Unlike the testing package which offers only basic capabilities for signalling failures, it offers ways to express expectations and get nice failure messages automatically.

Package testfs provides a simple fs.FS which is contained in a test (using testing.TB's TempDir) and with a few helper methods.

This package provides the Go source code for the go-staticcheck advanced Go linter.

Package gunit provides testing package hooks and convenience functions for writing tests in an xUnit style.

This package implements a functionality for testing socket and HTTP servers in Golang.

This package implements an extension of Table-Driven Testing. Instead of building and iterating over a table in the test code, the input is further separated into files (or inline strings). For certain classes of tests, this can significantly reduce the friction involved in writing and reading these tests.

This package provide many tools for testifying that your code will behave as you intend.

Features include:

• Easy assertions

• Mocking

• HTTP response trapping

• Testing suite interfaces and functions.

This library enables complex data structure testing, specifically:

• realtime transformation or casting of incompatible data types with directives system

• consistent way of testing of unordered structures

• contains, Range, RegExp support on any data structure deeph level

• switch case directive to provide expected value alternatives based on actual switch/case input match

• macro system enabling complex predicate and expression evaluation, and customization

The deep package provides the deep.Equal function which is like reflect.DeepEqual but returns a list of differences. This is helpful when comparing complex types like structures and maps.

This package provides additions to Go's stdlib testing.

Package assert provides obj set of assertion functions. Every assertion function returns obj boolean. This package does not integrate into the testing package automatically and requires to check the returning boolean value and call t.Fatal() if the assertion fails.

This package provides a test corpus of C code.

Package tbltest implements helper functions to help write table driven tests.

This package implements a functionality to scan and report for dependencies which are checked in to the repository. It provides a library and CLI tool.

This is a straight copy of the excellent Gomega library, stripped to the bare core to be free of third-party dependencies.

Package cienv implements some helper functions to use during tests. Many times certain facilities are not available, or tests must run differently.

A mini testing helper for Go.

• It has a simple interface (is.OK and is.Equal).

• It plugs into existing Go toolchain (uses testing.T).

• It's obvious for newcomers.

• It also gives you is.Panic and is.PanicWith helpers - because testing panics is ugly.

This package prints the layout of a struct in Go, which is the byte offset and size of each field, respecting padding. This information is printed in human-readable form by default, or as JSON with the -json flag.

gomock is a mocking framework for the Go programming language. It integrates well with Go's built-in testing package, but can be used in other contexts too.

assert is a testing library that provides high-level assertions API based on Go testing library procedures.

Package oglemock provides a mocking framework for unit tests.

Package spew implements a deep pretty printer for Go data structures to aid in debugging.

A quick overview of the additional features spew provides over the built-in printing facilities for Go data types are as follows:

• Pointers are dereferenced and followed.

• Circular data structures are detected and handled properly.

• Custom Stringer/error interfaces are optionally invoked, including on unexported types.

• Custom types which only implement the Stringer/error interfaces via a pointer receiver are optionally invoked when passing non-pointer variables.

• Byte arrays and slices are dumped like the hexdump -C command which includes offsets, byte values in hex, and ASCII output (only when using Dump style).