| commit | cbab26a46b5628418e536500bb1f4669a74cae5c | [log] [tgz] |
|---|---|---|
| author | onqtam <vik.kirilov@gmail.com> | Sat May 21 02:41:22 2016 +0300 |
| committer | onqtam <vik.kirilov@gmail.com> | Sun May 22 04:45:42 2016 +0300 |
| tree | ab5baef0468a0303e558b98ab14f1002e112d2d9 | |
| parent | c832deb7a4bf9ff00f25342570b9b76561c50b7b [diff] |
moving examples around
- examples/__dev_test_coverage/CMakeLists.txt[Added - diff]
- examples/__dev_test_coverage/main.cpp[Added - diff]
- scripts/how_subcases_work/CMakeLists.txt[Added - diff]
- scripts/how_subcases_work/main.cpp[Renamed from scripts/how_subcases_work.cpp - diff]
- scripts/linker_stress_test/CMakeLists.txt[Renamed from examples/linker_stress_test/CMakeLists.txt - diff]
- scripts/linker_stress_test/main.cpp[Renamed from examples/linker_stress_test/main.cpp - diff]
- scripts/linker_stress_test/readme.txt[Renamed from examples/linker_stress_test/readme.txt - diff]
- scripts/linker_stress_test/stress.inl[Renamed from examples/linker_stress_test/stress.inl - diff]
- scripts/linker_stress_test/test.cpp[Renamed from examples/linker_stress_test/test.cpp - diff]
- .clang-format
- .gitignore
- .gitmodules
- .travis.yml
- CHANGELOG.md
- CMakeLists.txt
- LICENSE.txt
- README.md
- appveyor.yml
- doc/
- doctest/
- examples/
- scripts/
the lightest feature rich C++ single header testing framework
The doctest library is inspired by the unittest {} functionality of the D programming language.
It is heavily influenced by Catch which is currently the most popular, simple and user friendly alternative out there.
The main differences are:
A complete compiling example with a self-registering test and a test runner looks like this:
#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN #include "doctest.h" int factorial(int number) { return number <= 1 ? number : factorial(number - 1) * number; } TEST_CASE("testing the factorial function") { CHECK(factorial(1) == 1); CHECK(factorial(2) == 2); CHECK(factorial(10) == 3628800); }
- Check out features and design goals to see why this library exists and how it is different from all the rest.
- Check out the tutorial here.
- a rich set of examples...
Build status
| Service | branch: master | branch: dev |
|---|---|---|
| Travis-CI (Linux/OSX) |  |  |
| Appveyor (Windows) | ||
| Unit Test Coverage |  |  |
| Static Analysis |  |
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 work on this project in my spare time and every cent is a big deal. I took a break from working in the industry to make open source software.
Contributions in the form of issues and pull requests are welcome as well.
Open an issue for a discussion before making a pull request to make sure the contribution goes smoothly.
This framework has some design goals which must be kept. Make sure you have read the features and design goals page.
The master branch is the stable one with the latest release and the dev branch is on the bleeding edge.
All the framework tests have their output collected when the CMake TEST_MODE variable is set to COLLECT (making the new reference output) and later the tests are ran on the CI services (travis and appveyor) - their output is compared with the current reference output in the repository with the COMPARE mode (default mode is NORMAL).
Code should be formatted with a recent-enough clang-format using the config file in the root of the repo (or I will do it...)
Testing with compilers different from GCC/Clang/MSVC (and more platforms) is something the project would benefit from.