catch3/include, 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







Merge pull request #701 from razeh/master
2016-09-22T16:44:14+00:00

Phil Nash

2016-09-22T16:44:14+00:00

c47c1797d262b6da07884eef490ae84d4319b90f

Fixes for XML encoding.




Fixes for XML encoding.






Do not trim test case names in the XML reporter.
2016-08-30T10:15:19+00:00

Igor Akhmetov

2016-08-30T09:54:02+00:00

02c7e41c7c1d38e26a5b323053d2a68ebe7338df

SCENARIO does not add leading spaces to the test name (only BDD-style section
names are modified), so the trimming is not necessary. But if the name is
trimmed, it makes it harder to correlate the output of XML reporter with tests
that have leading spaces in their name: e.g. these tests will have the same name
attribute:

TEST_CASE("Test") {}
TEST_CASE(" Test") {}





SCENARIO does not add leading spaces to the test name (only BDD-style section
names are modified), so the trimming is not necessary. But if the name is
trimmed, it makes it harder to correlate the output of XML reporter with tests
that have leading spaces in their name: e.g. these tests will have the same name
attribute:

TEST_CASE("Test") {}
TEST_CASE(" Test") {}







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












Use Clara v0.0.2.4 (updated) - fix for string lengths
2016-06-09T18:19:55+00:00

Phil Nash

2016-06-09T18:19:55+00:00

742457cbcf4756271eb12c86140100e64e35dac6