catch3/include/internal/catch_run_context.h, branch v2.13.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Improved generator tracking 2020-06-01T17:06:51+00:00 Martin Hořeňovský 2020-06-01T17:04:23+00:00 9500ded83b66ea02472833684135ab8573da5e2d * Successive executions of the same `GENERATE` macro (e.g. because of a for loop) no longer lead to multiple nested generators. * The same line can now contain multiple `GENERATE` macros without issues. Fixes #1913 
* Successive executions of the same `GENERATE` macro (e.g. because
of a for loop) no longer lead to multiple nested generators.
* The same line can now contain multiple `GENERATE` macros without
issues.

Fixes #1913
Introduce Catch's own RNG based on the PCG family of RNGs 2019-10-07T17:56:23+00:00 Martin Hořeňovský 2019-10-06T19:47:54+00:00 535da5c5132bcbba6f29c60ed6bb7ded29b9ec3e In the future, we will also want to introduce our own `uniform_int_distribution` and `uniform_real_distribution` to get repeatable test runs across different platforms. 
In the future, we will also want to introduce our own
`uniform_int_distribution` and `uniform_real_distribution` to get
repeatable test runs across different platforms.
Various improvements to the benchmarking support 2019-06-06T19:28:56+00:00 Martin Hořeňovský 2019-05-19T18:54:44+00:00 e340ab8db6dbe07a58b6e72a9364d67d2178293c * Units from <ratio> are no longer redeclared in our own namespace * The default clock is `steady_clock`, not `high_resolution_clock`, because, as HH says "high_resolution_clock is useless. If you want measure the passing of time, use steady_clock. If you want user friendly time, use system_clock". * Benchmarking support is opt-in, not opt-out, to avoid the large (~10%) compile time penalty. * Benchmarking-related options in CLI are always present, to decrease the amount of code that is only compiled conditionally and making the whole shebang more maintainble. 
* Units from <ratio> are no longer redeclared in our own namespace
* The default clock is `steady_clock`, not `high_resolution_clock`,
because, as HH says "high_resolution_clock is useless. If you want
measure the passing of time, use steady_clock. If you want user
friendly time, use system_clock".
* Benchmarking support is opt-in, not opt-out, to avoid the large
(~10%) compile time penalty.
* Benchmarking-related options in CLI are always present, to decrease
the amount of code that is only compiled conditionally and making
the whole shebang more maintainble.
Integrate Nonius benchmark into Catch2 2019-06-06T17:33:37+00:00 Joachim Meyer 2019-04-23T21:41:13+00:00 ce2560ca956c1743f8bc871e0bf95f65a3db887c Changes done to Nonius: * Moved things into "Catch::Benchmark" namespace * Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros * Removed Nonius's parameters for benchmarks, Generators should be used instead * Added relevant methods to the reporter interface (default-implemented, to avoid breaking existing 3rd party reporters) * Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default on MSVC * Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of benchmarking from Catch 
Changes done to Nonius:
* Moved things into "Catch::Benchmark" namespace
* Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros
* Removed Nonius's parameters for benchmarks, Generators should be used instead
* Added relevant methods to the reporter interface (default-implemented, to avoid
breaking existing 3rd party reporters)
* Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default
on MSVC
* Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of
benchmarking from Catch
Add unscoped info functionality 2019-03-06T21:04:35+00:00 Omer Ozarslan 2019-02-01T15:11:30+00:00 99575b45db0ec0de2fb84b5e5cce7e93559387e5 This adds UNSCOPED_INFO macro, creating a log message that is stored until the end of next assertion or the end of test case, whichever comes first. These messages are not scoped locally, unlike messages created by INFO macro. 
This adds UNSCOPED_INFO macro, creating a log message that is stored
until the end of next assertion or the end of test case, whichever comes
first. These messages are not scoped locally, unlike messages created by
INFO macro.
RunContext: Uninit Member 2019-01-13T09:26:47+00:00 Axel Huebl 2019-01-07T17:55:33+00:00 47602ac5569b77ad1781f8a257451b05fe180844 Fix an uninitialized member in `RunContext`. Found with coverity in a downstream project. 
Fix an uninitialized member in `RunContext`.

Found with coverity in a downstream project.
First attempt at data generator support 2018-08-24T11:31:51+00:00 Phil Nash 2018-06-12T16:50:39+00:00 7c25dae9ea7b669430103d29cd262abb0842f4e5 The support is to be considered experimental, that is, the interfaces, the first party generators and helper functions can change or be removed at any point in time. Related to #850 
The support is to be considered experimental, that is, the interfaces,
the first party generators and helper functions can change or be removed
at any point in time.

Related to #850
Fix clang-tidy 6 diagnostic about virtual call in destructor 2018-03-21T16:05:15+00:00 Zsolt Parragi 2018-03-15T20:23:33+00:00 886d799b79ca7873913fc3bb048db3b6a64dc47b 






Refactored StreamRedirect classes
2017-12-05T23:19:28+00:00

Phil Nash

2017-12-05T23:19:28+00:00

aa9d635014c3ab321fe65bd59c50fa71d6a86583












Revirtualised IResultCapture methods
2017-12-05T16:23:10+00:00

Phil Nash

2017-12-05T16:18:53+00:00

533cdc6bc137381f8a358e15d97289917c2df6c5

Didn't really impact runtime anyway, but will need to use interface for threading support.





Didn't really impact runtime anyway, but will need to use interface for threading support.