1.stretchr / testify
A toolkit with common assertions and mocks that plays nicely with the standard library
Ranked by Attention Score: stars gained over the last 30 complete days
16 repositories by Attention Score · Oct 4, 2026 – Nov 2, 2026 (UTC)
A toolkit with common assertions and mocks that plays nicely with the standard library
A light-weight, flexible, and expressive statistical data testing library
Test Automation Made Simple
Pester is the ubiquitous test and mock framework for PowerShell.
🕷 Super-agent driven library for testing node.js HTTP servers using a fluent API. Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.
Type check values
Extremely flexible golang deep comparison, extends the go testing package, tests HTTP APIs and provides tests suite
AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.
zerocode-tdd is a community-developed, free, open-source, outcome-driven automated testing framework for Data Pipelines, ETL, REST API, Kafka(Data Streams), Databases and Load scenarios. all defined in simple JSON or YAML — with zero coding.
End-to-end HTTP and REST API testing for Go.
The most over-engineered C++ assertion library
A collection of packages to augment the go testing package and support common patterns.
Micro toolkit for Clojure/Script errors
A Go test assertion library for verifying that two representations of JSON are semantically equal