doctest icon indicating copy to clipboard operation
doctest copied to clipboard

The fastest feature-rich C++11/14/17/20/23 single-header testing framework

Results 244 doctest issues
Sort by recently updated
recently updated
newest added

## Description As of this time, when using doctest with fixture classes, there is no way to write common fixture teardown code outside of the fixture destructor. When doing so...

## Description I'm porting some tests from Catch2 to doctest and I'm trying to pretty print some of our templated test cases. But for some some cases we don't template...

verdict/wontfix

## Description Some classes have private methods which cannot be conveniently tested through a public interface. What is the recommended way to test a private method using doctest? ### Extra...

verdict/stale
has-workaround

I'm trying to use Doctest to test a 3D renderer. I would like to set it up such that each renderer frame runs 1 test-case. The renderer would write frame...

## Description Using either `g++` or `mingw x86_64-w64-mingw32-g++-posix` cross-compiler I generate valid (64 bit) executables. However, I fail to get a valid 32 executable: `g++ -m32` or `mingw i686-w64-mingw32-g++-posix `...

I find this very simple macro very useful for testing constexpr code using doctest: //fails compilation if the check fails, reports at runtime if it succeeds #define STATIC_REQUIRE(x) static_assert(x); REQUIRE(x)

## Description I have a test case that forks and the forked process sometimes calls `abort()`. Unfortunately doctest's signal handler is active in the child process too and it produces...

verdict/wontfix

## Description I don't know if this can be considered a bug, but if you register a reporter with the same name as an already existing one, when you select...

type/bug
category/reporting

I am trying to come up with a TEST_CASE_CLASS-like macro that can be used to wrap a class and provide access to protected variables, but does not have to be...

verdict/stale
type/feature-proposal
category/API-usage

Most, if not all, mock frameworks out there require to declare the expected callbacks BEFORE executing the stimulus on the SUT. This defers from the regular pattern of GIVEN/WHEN/THEN where...

category/BDD
type/feature-proposal