c4b3a5097ff9ff03ff03bb4641c8efd1d68e7534 - github/onqtam/doctest

commit	c4b3a5097ff9ff03ff03bb4641c8efd1d68e7534	[log] [tgz]
author	onqtam <vik.kirilov@gmail.com>	Sun May 01 22:46:16 2016 +0300
committer	onqtam <vik.kirilov@gmail.com>	Tue May 03 19:03:53 2016 +0300
tree	d46fa7ed684791cfc35feb4b6ffe5a6518927003
parent	3c239731f93a30d7784aa25cf6a15b6cba5485ee [diff]

tree: d46fa7ed684791cfc35feb4b6ffe5a6518927003

README.md

the lightest and feature rich C++ single header testing framework

The doctest library is inspired by the unittest functionality of the D programming language and the docstrings in python - tests can be considered a form of documentation and should be able to reside near the production code which they test.

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.

Note that only GCC/Clang/MSVC as compilers have been tested and warnings have been silenced only for them so this might be an area worth exploring...