catch3/include/internal, branch v1.5.7 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Build 1.5.7 2016-09-27T09:46:22+00:00 Phil Nash 2016-09-27T09:46:22+00:00 40f6068d5223409a4eecdacee08572e9118b2137 






--list-test-names quotes test names that start with #
2016-09-27T09:43:03+00:00

Phil Nash

2016-09-27T09:43:03+00:00

21cbfc107e41710266ec9a6f3725aed9e47620cc

- completes #717





- completes #717







-f supports quoted test names (test name surrounded with " characters).
2016-09-27T09:27:28+00:00

Phil Nash

2016-09-27T09:27:28+00:00

b1eeec7c6976ac23b3d28986eff93d605a7f12e7

This is the first part to resolving #717





This is the first part to resolving #717







Added braces to emphasise the return logic
2016-09-27T08:58:12+00:00

Phil Nash

2016-09-27T08:58:12+00:00

c23b374f3dea7e51bb0acf676c993d82a34db190












Fix misindent
2016-09-26T22:35:26+00:00

nabijaczleweli

2016-07-04T10:44:08+00:00

8c459dd207b541b68664db33026361a3ee491a44

Closes #679





Closes #679







Fixes for XML encoding.
2016-08-24T14:38:24+00:00

Robert A Zeh

2016-08-24T14:38:24+00:00

5095619955f9f408e503dfcf561923ac6e48e3ce

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





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







v1.5.6
2016-06-09T18:21:09+00:00

Phil Nash

2016-06-09T18:21:09+00:00

35f510545d55a831372d3113747bf1314ff4f2ef












Fixed RNG issue with pre C++14 compilers
2016-06-09T18:07:05+00:00

Phil Nash

2016-06-09T18:07:05+00:00

1aa6c91e6428d3f25bc4329ef6eb7938cd53a157












v1.5.5:
2016-06-09T07:19:23+00:00

Phil Nash

2016-06-09T07:19:23+00:00

ac220289a617481b05b4d7821a19a89ba20d282c

Deal with auto_ptr and random_shuffle hard deprecations in C++14





Deal with auto_ptr and random_shuffle hard deprecations in C++14







Use std::shuffle instead of (deprecated) std::random_shuffle if C++14 detected
2016-06-09T07:15:57+00:00

Phil Nash

2016-06-09T07:15:57+00:00

be3570ef22a450e7e040913822828468f70d7f81