Gitiles
Code Review Sign In
gerrit.cesnet.cz / github / onqtam / doctest / 02af672f0d3093157daecb55ce4e109ffaf2bc53
commit02af672f0d3093157daecb55ce4e109ffaf2bc53[log] [tgz]
authoronqtam <vik.kirilov@gmail.com>Thu Dec 09 17:00:02 2021 +0200
committeronqtam <vik.kirilov@gmail.com>Fri Dec 10 23:41:29 2021 +0200
tree1b77c66b6b8711182631397e6bc990371303589e
parentf0229ac244a8e6cb27cae650316c899c78d01cdd [diff]
Fixes Issues #476 and #495

* Fixes Issue #476 . When running executables with  stringifyBinaryExpr was accessing memory beyond bounds.This is because there is no '\0' in certain structures like  span or fixed size array. A specialization is added for array T[N]  which fills N objects of type T and then in the ostream appends an empty string without resetting the stream everytime.

* Fix for #495 struct packed members which are not aligned properly and doesn't bind to universal reference. The best way to fix this is in the caller's code like annotating with CHECK (as_const(packedFoo.bar) == 0) or CHECK( static_cast <const T&> (packedFoo.bar) == 0 ). Also packedFoo.bar doesn't work with c++11/14 make_pair. The code which fails to compile with gcc works with clang without any change.

This is the result of PR #491
https://github.com/doctest/doctest/pull/491/commits/28a9dd82e8203a05f0afb7b1412c86737803e212
4 files changed
tree: 1b77c66b6b8711182631397e6bc990371303589e
  1. .clang-format
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .travis.yml
  7. CHANGELOG.md
  8. CMakeLists.txt
  9. CONTRIBUTING.md
  10. LICENSE.txt
  11. README.md
  12. WORKSPACE
  13. appveyor.yml
  14. doc/
  15. doctest/
  16. examples/
  17. meson.build
  18. scripts/
README.md

doctest is a new C++ testing framework but is by far the fastest both in compile times (by orders of magnitude) and runtime compared to other feature-rich alternatives. It brings the ability of compiled languages such as D / Rust / Nim to have tests written directly in the production code thanks to a fast, transparent and flexible test runner with a clean interface.

Standard License download CII Best Practices Language grade: C/C++ Join the chat at https://gitter.im/onqtam/doctest Try it online

The framework is and will stay free but needs your support to sustain its development. There are lots of new features and maintenance to do. If you work for a company using doctest or have the means to do so, please consider financial support. Monthly donations via Patreon and one-offs via PayPal.

A complete example with a self-registering test that compiles to an executable looks like this:

cover-example

There are many C++ testing frameworks - Catch, Boost.Test, UnitTest++, cpputest, googletest and many other.

The key differences between it and other testing frameworks are that it is light and unintrusive:

  • Ultra light on compile times both in terms of including the header and writing thousands of asserts
  • Doesn't produce any warnings even on the most aggressive warning levels for MSVC/GCC/Clang
  • Offers a way to remove everything testing-related from the binary with the DOCTEST_CONFIG_DISABLE identifier
  • thread-safe - asserts (and logging) can be used from multiple threads spawned from a single test case - example
  • asserts can be used outside of a testing context - as a general purpose assert library - example
  • Doesn't pollute the global namespace (everything is in namespace doctest) and doesn't drag any headers with it
  • Very portable C++11 (use tag 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

cost-of-including-the-framework-header

This allows the framework to be used in more ways than any other - tests can be written directly in the production code!

Tests can be considered a form of documentation and should be able to reside near the production code which they test.

  • This makes the barrier for writing tests much lower - you don't have to: 1) make a separate source file 2) include a bunch of stuff in it 3) add it to the build system and 4) add it to source control - You can just write the tests for a class or a piece of functionality at the bottom of its source file - or even header file!
  • Tests in the production code can be thought of as documentation or up-to-date comments - showing the use of APIs
  • Testing internals that are not exposed through the public API and headers is no longer a mind-bending exercise
  • Test-driven development in C++ has never been easier!

The framework can be used like any other if you don't want/need to mix production code and tests - check out the features.

doctest is modeled after Catch and some parts of the code have been taken directly - check out the differences.

This table compares doctest / Catch / lest which are all very similar.

Checkout the CppCon 2017 talk on YouTube to get a better understanding of how the framework works and read about how to use it in the JetBrains article - highlighting the unique aspects of the framework! On a short description on how to use the framework along production code you could refer to this GitHub issue. There is also an older article in the february edition of ACCU Overload 2017.

CppCon 2017 talk about doctest on youtube

Documentation

Project:

Usage:

Contributing

Support the development of the project with donations! There is a list of planned features which are all important and big - see the roadmap. I took a break from working in the industry to make open source software so every cent is a big deal.

If you work for a company using doctest or have the means to do so, please consider financial support.

Contributions in the form of issues and pull requests are welcome as well - check out the Contributing page.

Logo

The logo is licensed under a Creative Commons Attribution 4.0 International License. Copyright © 2019 area55git   License: CC BY 4.0