Testify/v2

---

The v2 our tests wanted

A set of go packages that provide tools for testifying (verifying) that your code behaves as you intended.

This is the go-openapi fork of the great testify package.

[!NOTE] This is the home of github.com/go-openapi/testify/v2, an active, opinionated fork of github.com/stretchr/testify.

Why choose go-openapi/testify/v2

• 95% compatible with stretchr/testify — if you already use it, our migration tool automates the switch
• Actively maintained: regular fixes and evolutions, many PRs proposed upstream are already in. See our tracking board
• Zero external dependencies — you import what you need, with opt-in modules for extras (e.g. YAML, colorized output)
• Modernized codebase targeting go1.26+
• Go routine leak detection built in: zero-setup, no false positives, works with parallel tests (unlike go.uber.org/goleak)
• File descriptor leak detection (linux-only)
• Type-safe assertions with generics (see a basic example) — migration to generics can be automated too. Read the full story
• Safe async assertions, extended JSON & YAML assertions
• Non-flaky async assertions using synctest, and internal tools exposed as standalone modules (spew, unified diff, goleak)
• Extensible Assertion type
• We take documentation seriously: searchable doc site with testable examples and a complete tutorial, plus detailed godoc for every assertion

This fork isn't for everyone

• You need the mock package — we removed it and won't bring it back. For suites, we're open to discussion about a redesigned approach
• Your project must support Go versions older than 1.26
• You rely on testifylint or other tooling that expects the stretchr/testify import path
• You need 100% API compatibility — we're at 95%, and the remaining 5% are intentional removals

Announcements

• 2026-09-07 :

  • v2.8.0 lands today - go1.26 is now required

• 2026-08-23 :

  • v2.7.0 lands today - for go1.27, users generic assertions are now available as methods
  • v2.8.0 will land end of Sept., with go1.26+ required
  • besides patch releases, only one more minor release v2.9.0 is currently planned till the end of this year: the contemplated topic is the revival of test suites.

• 2026-08-08 : v2.7.0 landing soon (ETA Sept. 2026)

• 2026-06-22 : ROADMAP to v2.7.0 (ETA Sept. 2026)

  • minor version releases will slow down from monthly to quarterly. Next planned for September
  • go1.27 optional support, with forward methods supporting generics.

Status

Design and exploration phase completed. The published API is now stable: moving forward, API changes will remain backward-compatible with v2.4.0.

Feedback, contributions and proposals are welcome.

Getting started

Import this library in your project like so.

go get github.com/go-openapi/testify/v2

... and start writing tests. Look at our examples.

Basic usage

testify simplifies your test assertions like so.

import (
        "testing"
    )
    ...

    const expected = "expected result"

	result := printImports(input)
	if result != expected {
		t.Errorf(
            "Expected: %s. Got: %s", expected, result,
        )

        return
	}

Becomes:

import (
        "testing"
        "github.com/go-openapi/testify/v2/require"
    )
    ...

    const expected = "expected result"

	require.Equalf(t,
        expected, printImports(input), "Expected: %s. Got: %s",
        expected, result,
    )

Usage at go-openapi and go-swagger

This fork now fully replaces the original project for all go-openapi projects, thus reducing their dependencies footprint.

Go-swagger has also adopted it. Now the work is to generalize the use of generics (leveraging our migration tool).

Features might be added to support our main use cases there.

Change log

See https://github.com/go-openapi/testify/releases

Licensing

SPDX-FileCopyrightText: Copyright 2025 go-swagger maintainers

This library ships under the SPDX-License-Identifier: Apache-2.0.

See the license NOTICE, which recalls the licensing terms of all the pieces of software distributed with this fork, including internalized libraries.

We'd like to give credit and pay a big and loud thank you to the people who wrote these amazing pieces of software. We maintain their original work here and continue improving it.

• Mat Ryer, Tyler Bunnell and the stretchr/testify contributors - who made this new project possible
• thank you to the maintainers of that library, @ccoveille, @dolmen for their feedback and advice
• Dave Collins [email protected] who wrote the spew library
• Patrick Mezard who wrote the difflib library - originally a go port from python's difflib

Also special thanks to:

• Gregory Petrosyan (@flyingmutant) - we use his amazing "rapid" library for our integration tests, with property-based testing
• the authors and maintainers of github.com/yaml/go-yaml, which we rely on for our YAML work

Other documentation

• Getting started

• Usage

• Motivations

• Roadmap

• Internal architecture

• Benchmarks

• All-time contributors

• Contributing guidelines

• Maintainers documentation

• Coding style

• Security policy

Cutting a new release

Maintainers can cut a new release by either:

• running this workflow (recommended)
• or :
  1. preparing go.mod files with the next tag, merge
  2. pushing a semver tag
  • signed tags are preferred
  • The tag message is prepended to release notes