A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
Go to file
Robert A Zeh 5095619955 Fixes for XML encoding.
This commit fixes the following scenario:
  * You have a test that compares strings with embedded control
  characters.
  * The test fails.
  * You are using JUnit tests within TeamCity.

Before this commit, the JUnit report watcher fails on parsing the XML
for two reasons: the control characters are missing a semicolon at the
end, and the XML document doesn't specify that it is XML 1.1.

XML 1.0 --- what we get if we don't specify an XML version --- doesn't support embedding control characters --- see
http://stackoverflow.com/questions/404107/why-are-control-characters-illegal-in-xml
for all of the gory details.

This is based on PR #588 by @mrpi
2016-08-24 09:38:24 -05:00
docs Update tutorial.md 2016-04-04 23:04:45 -03:00
include Fixes for XML encoding. 2016-08-24 09:38:24 -05:00
projects Fixes for XML encoding. 2016-08-24 09:38:24 -05:00
scripts Removed unnecessary parentheses 2015-11-04 18:49:19 +00:00
single_include v1.5.6 2016-06-09 19:21:09 +01:00
.gitattributes Git Attributes, with control for line-endings 2013-10-18 07:53:05 +01:00
.gitignore Ignore *.xccheckout 2015-03-27 17:55:13 +00:00
.travis.yml Pins LLVM 3.8 (stable) instead of tracking the nightly repository 2016-05-07 18:55:12 +02:00
LICENSE_1_0.txt Fixed crlf issue 2013-11-07 13:05:29 +01:00
README.md v1.5.6 2016-06-09 19:21:09 +01:00
catch-logo-small.png Added logo to readme 2013-03-21 19:12:21 +00:00

README.md

catch logo

v1.5.6

Build status (on Travis CI) Build Status

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:

More