diff options
author | onqtam <vik.kirilov@gmail.com> | 2018-11-29 17:42:07 +0300 |
---|---|---|
committer | onqtam <vik.kirilov@gmail.com> | 2018-11-29 17:43:29 +0300 |
commit | 25203777ad5acf89142f168158c5c4c0dea9805f (patch) | |
tree | c8c44c9754b21972f0192608ea3fdb6185405870 /README.md | |
parent | 55d9f05629fecce8c2a747463f3234be99cc5d04 (diff) |
small docs fixes
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -55,11 +55,11 @@ The **key** differences between it and other testing frameworks are that it is l - Ultra light on compile times both in terms of [**including the header**](doc/markdown/benchmarks.md#cost-of-including-the-header) and writing [**thousands of asserts**](doc/markdown/benchmarks.md#cost-of-an-assertion-macro) - Doesn't produce any warnings even on the [**most aggressive**](scripts/cmake/common.cmake#L84) warning levels for **MSVC**/**GCC**/**Clang** - Offers a way to remove **everything** testing-related from the binary with the [**```DOCTEST_CONFIG_DISABLE```**](doc/markdown/configuration.md#doctest_config_disable) identifier -- [**thread-safe**](faq.md#is-doctest-thread-aware) - asserts (and logging) can be used from multiple threads spawned from a single test case - [**example**](../../examples/all_features/concurrency.cpp) +- [**thread-safe**](faq.md#is-doctest-thread-aware) - asserts (and logging) can be used from multiple threads spawned from a single test case - [**example**](examples/all_features/concurrency.cpp) - asserts can be used [**outside of a testing context**](doc/markdown/assertions.md#using-asserts-out-of-a-testing-context) - as a general purpose assert library - [**example**](examples/all_features/asserts_used_outside_of_tests.cpp) - Doesn't pollute the global namespace (everything is in namespace ```doctest```) and doesn't drag **any** headers with it - Very [**portable**](doc/markdown/features.md#extremely-portable) C++11 (use tag [**1.2.9**](https://github.com/onqtam/doctest/tree/1.2.9) for C++98) with over 180 different CI builds (static analysis, sanitizers...) -- binaries (exe/dll) can use the test runner of another binary - so tests end up in a single registry - [**example**](../../examples/executable_dll_and_plugin/) +- binaries (exe/dll) can use the test runner of another binary - so tests end up in a single registry - [**example**](examples/executable_dll_and_plugin/) ![cost-of-including-the-framework-header](scripts/data/benchmarks/header.png) |