This package provides additions to Go's stdlib fmt.

This package provides helpers for automated testing of scanners/lexers/tokenizers.

Package quicktest provides a collection of Go helpers for writing tests.

This package provides a contract to share variables between test helpers in Golang.

Ginkgo is a Behaviour-Driven Development testing framework for Go. It builds on top of Go's builtin testing library and is complemented by the Gomega matcher library.

Package stub provides helper functions to replace global variables for testing, and restore them afterwards.

Rapid is a Go library for property-based testing.

Rapid checks that properties you define hold for a large number of automatically generated test cases. If a failure is found, rapid automatically minimizes the failing test case before presenting it.

Features:

• imperative Go API with type-safe data generation using generics

• data generation biased to explore "small" values and edge cases more thoroughly

• fully automatic minimization of failing test cases

• persistence and automatic re-running of minimized failing test cases

• support for state machine ("stateful" or "model-based") testing

• no dependencies outside the Go standard library

This package provides basic assertions along with building blocks for custom assertions to be used alongside native Go testing.

Package st, pronounced ghost, is a tiny test framework for making short, useful assertions in your Go tests. Assert(t, have, want) and Refute(t, have, want) abort a test immediately with t.Fatal. Expect(t, have, want) and Reject(t, have, want) allow a test to continue, reporting failure at the end with t.Error. They print nice error messages, preserving the order of have (actual result) before want (expected result) to minimize confusion.

This package implement a functionality for validating tags according to rules you define and fixing them according to the defined rules.

Package sloglint implements the sloglint analyzer. The log/slog API allows two different types of arguments: key-value pairs and attributes.

A testing library for Go programs.

This package implements a functionality to mock a PostgreSQL server.

This package provides a quick and easy string diffing functions based on github.com/sergi/go-diff, mainly for diffing strings in tests.

The Test Anything Protocol is a text-based interface between tests and a test harness. This package helps Go to generate TAP output.

Package fake is the fake data generatror for go (Golang), heavily inspired by forgery and ffaker Ruby gems.

Correct is a collection of assertion libraries for Golang, intended to be used together. It tries not to strictly enforce that, though - most of correct should be customizeable either by changing some options or by using only some sub-packages of correct.

This package provides scripts and workflows to automate common routines for Golang projects via modular Makefiles and GitHub Actions.

Reports unused function parameters and results in Go code.

This package takes go-structlayout-like JSON and prints an ASCII fraphic representing the memory layout.

This package provides tools for detecting deadlocks at run-time in Go.

Package testza is a full-featured testing framework for Go. It integrates with the default test runner, so you can use it with the standard go test tool. Testza contains easy to use methods, like assertions, output capturing, mocking, and much more.

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.

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).