| commit | 1da586cfe2e96e9d4ceb47fc753477a6c180a15e | [log] [tgz] |
|---|---|---|
| author | onqtam <vik.kirilov@gmail.com> | Mon May 09 19:18:38 2016 +0300 |
| committer | onqtam <vik.kirilov@gmail.com> | Mon May 09 19:18:38 2016 +0300 |
| tree | b87b1b69aadb42da92eb0605bbe172420e607310 | |
| parent | 9cccba70f4ae4325c3aa77bb29f3d5af3cb6ab96 [diff] |
the example in it's simplest form
- examples/trololo/CMakeLists.txt[diff]
- examples/trololo/in.h[diff]
- examples/trololo/main.cpp[diff]
- examples/trololo/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 and Python's docstrings - tests can be considered a form of documentation and should be able to reside near the production code which they test.
It is modeled after Catch (and lest) which is currently the most popular, simple and user friendly library out there.
- 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.
Build status
| Service | branch: master | branch: dev |
|---|---|---|
| Travis-CI (Linux/OSX) |  |  |
| Appveyor (Windows) | ||
| Unit Test Coverage |  |  |
| Static Analysis |  |
Contributing
Donations would be appreciated very much since I quit my job to write open source software.
Contributions in the form of issues and pull requests are welcome as well.
For pull requests make sure the code is formatted with a recent-enough clang-format using the config file in the root of the repo (or I will format it after the merge) and that all the builds on travis and appveyor pass. Also before making a pull requrest you might want to make an issue about it for a discussion or join the chat on gitter.
This library 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.
Testing with compilers different from GCC/Clang/MSVC (and more platforms) is something the project would benefit from.