gerrit-public.fairphone.software / platform / external / catch2 / 21f7ef6fdcfcc98fa668028c02ba51643982e7cf
| commit | 21f7ef6fdcfcc98fa668028c02ba51643982e7cf | [log] [tgz] |
|---|---|---|
| author | Phil Nash <github@philnash.me> | Mon Jun 29 18:05:23 2015 +0100 |
| committer | Phil Nash <github@philnash.me> | Mon Jun 29 18:06:15 2015 +0100 |
| tree | bdf6b9ca32777405feeefa8a6f5e34481fe6f468 | |
| parent | f5fef1ebed9faaf12058d7a16223b4f617e6a5b6 [diff] |
Committed to semantic versioning as prompted by #365, #430, #447 and a thread on the google group. - split version bumping out of generateSingleHeader script - separate scripts for bumping each version component - "build" number only incremented for "develop" builds
- README.md[diff]
- docs/contributing.md[diff]
- include/catch_runner.hpp[diff]
- include/internal/catch_version.h[diff]
- include/internal/catch_version.hpp[diff]
- include/reporters/catch_reporter_console.hpp[diff]
- scripts/developBuild.py[Added - diff]
- scripts/generateSingleHeader.py[diff]
- scripts/majorRelease.py[Added - diff]
- scripts/minorRelease.py[Added - diff]
- scripts/patchRelease.py[Added - diff]
- scripts/releaseCommon.py[Added - diff]
- single_include/catch.hpp[diff]
13 files changed
tree: bdf6b9ca32777405feeefa8a6f5e34481fe6f468
- docs/
- include/
- projects/
- scripts/
- single_include/
- .gitattributes
- .gitignore
- .travis.yml
- catch-logo-small.png
- LICENSE_1_0.txt
- README.md
README.md
v1.2.0
Build status (on Travis CI) 
Please see this page if you are updating from a version before 1.0
[The latest, single header, version can be downloaded directly using this link]
What's the Catch?
Catch stands for C++ Automated Test Cases in Headers and is a multi-paradigm automated test framework for C++ and Objective-C (and, maybe, C). It is implemented entirely in a set of header files, but is packaged up as a single header for extra convenience.
How to use it
This documentation comprises these three parts:
- Why do we need yet another C++ Test Framework?
- Tutorial - getting started
- Reference section - all the details
The documentation will continue until morale improves
More
- Issues and bugs can be raised on the Issue tracker on GitHub
- For discussion or questions please use the dedicated Google Groups forum