4636be9744
* NewSectionTracking: Added SUCCEEDs to empty leaf sections to avoid failing due to no assertions Removed deprecated section tracking implementation and tests Approved changes due to "No assertions" warnings now firing correctly on inner sections perform startRun() at the start of each test case Fitted new section tracking Converted all new part tracking tests/ sections to non variadic form Moved all new tracking impl into catch_test_case_tracker.pp Removed the "part" component of the tracker names More minor tweaks Added tests for failing a section within a generator - small fixes to implementation to make it work more minor clean-ups Cleaned tests up a bit Added IndexTracker and got it working with a single generator - made some simplifications to state machine More name changes Tweaks First cut of new section/ part tracking Refactored stream related stuff - simpler, polymorphic hierarchy-based, approach - less bitty conditionals spread across the code - all resolved up-front so now config class is immutable (it had evolved the way it was and in need of a clean-up sweep for a long time) Some small clean-ups and refactorings - removed previous instance saves in RunContext (they were a hang-over from embedded contexts) - started cleaning up config usage |
||
---|---|---|
docs | ||
include | ||
projects | ||
scripts | ||
single_include | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
catch-logo-small.png | ||
LICENSE_1_0.txt | ||
README.md |
v1.2.1-develop.14
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