gerrit-public.fairphone.software / platform / external / catch2 / c390c4cb9f9ae384451a5b8cda08aebf34407207
| commit | c390c4cb9f9ae384451a5b8cda08aebf34407207 | [log] [tgz] |
|---|---|---|
| author | Martin Hořeňovský <martin.horenovsky@gmail.com> | Thu Jan 26 23:13:12 2017 +0100 |
| committer | Martin Hořeňovský <martin.horenovsky@gmail.com> | Thu Jan 26 23:13:12 2017 +0100 |
| tree | 79cb91867deabac9974094a6b2323ea8b8f2a2f4 | |
| parent | 60a9ac7e65a57d82a92eebb7c8c6c1111a75897e [diff] |
Fixed inconsistent and trailing whitespace This means that all tabs used in indentation are now 4 spaces and that there should be no more trailing whitespace. Ill also look into creating a pre-commit hook that will prevent this from happening in the future. Fixes #105
- include/internal/catch_commandline.hpp[diff]
- include/internal/catch_fatal_condition.hpp[diff]
- include/internal/catch_interfaces_config.h[diff]
- include/internal/catch_interfaces_reporter.h[diff]
- include/internal/catch_test_case_tracker.hpp[diff]
- include/internal/catch_tostring.hpp[diff]
- include/reporters/catch_reporter_bases.hpp[diff]
- include/reporters/catch_reporter_multi.hpp[diff]
- include/reporters/catch_reporter_xml.hpp[diff]
- projects/SelfTest/ApproxTests.cpp[diff]
- projects/SelfTest/BDDTests.cpp[diff]
- projects/SelfTest/ConditionTests.cpp[diff]
- projects/SelfTest/ExceptionTests.cpp[diff]
- projects/SelfTest/TestMain.cpp[diff]
- scripts/fixWhitespace.py[Renamed from scripts/fixTrailingWhitespace.py - diff]
15 files changed
tree: 79cb91867deabac9974094a6b2323ea8b8f2a2f4
- docs/
- include/
- projects/
- scripts/
- single_include/
- .gitattributes
- .gitignore
- .travis.yml
- catch-logo-small.png
- catch-logo-tiny.png
- CMakeLists.txt
- LICENSE_1_0.txt
- README.md
README.md
v1.6.1
Build status (on Travis CI) 
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
More
- Issues and bugs can be raised on the Issue tracker on GitHub
- For discussion or questions please use the dedicated Google Groups forum