catch3/include/internal/catch_xmlwriter.hpp, branch v1.7.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. XML Reporter closes tag and flushes stream at end of TestCase and Section tags. 2017-02-13T15:56:25+00:00 Phil Nash 2017-02-13T15:56:25+00:00 873ef276b6be03f0cdc7c95a76e98b8942b32cbc This fixes an issue where XML reports on stdout are broken by printf statements 
This fixes an issue where XML reports on stdout are broken by printf statements
XmlWriter can specify a stylesheet 2017-02-07T23:09:43+00:00 Phil Nash 2017-02-07T23:09:43+00:00 97d8003a713117df078208c55cd762e135396359 Provide an extension point on XmlReporter to be able to supply a stylesheet url in a derived implementation 
Provide an extension point on XmlReporter to be able to supply a stylesheet url in a derived implementation
XmlWriter reverts to XML 1.0. 2017-02-07T22:48:06+00:00 Phil Nash 2017-02-06T16:00:05+00:00 1f271c99447048a67b8abce45ee1a8f848f60869 Character encodings that are not valid in XML 1.0 are instead written using C-style escapes 
Character encodings that are not valid in XML 1.0 are instead written using C-style escapes
XmllWriter flushes the stream after every endElement now 2017-02-06T16:25:36+00:00 Phil Nash 2017-02-06T16:25:36+00:00 84af6bc955491d4b2a4c1d3c61e0b3516ce9f298 






Revert "XmlWriter reverts to XML 1.0."
2017-02-06T16:21:01+00:00

Phil Nash

2017-02-06T16:21:01+00:00

88b760276dc6bcff877dae439998810f189f32ca

This reverts commit a189387f49f129a3554c47426a0dfe176c5c0781.





This reverts commit a189387f49f129a3554c47426a0dfe176c5c0781.







XmlWriter reverts to XML 1.0.
2017-02-06T16:00:05+00:00

Phil Nash

2017-02-06T16:00:05+00:00

a189387f49f129a3554c47426a0dfe176c5c0781

Character encodings that are not valid in XML 1.0 are instead written using C-style escapes





Character encodings that are not valid in XML 1.0 are instead written using C-style escapes







Use char literal instead of string literal with 1 char
2017-01-29T22:07:15+00:00

Martin Hořeňovský

2017-01-29T22:07:15+00:00

bcaa2f9646c5ce50758f8582307c99501a932e1a

In reality, this is a relatively small performance improvement,
especially with the previous improvements removing lots of superfluous
string handling, but still was measurable.





In reality, this is a relatively small performance improvement,
especially with the previous improvements removing lots of superfluous
string handling, but still was measurable.







Various small string usage performance improvements.
2017-01-15T09:05:01+00:00

Martin Hořeňovský

2017-01-15T08:41:33+00:00

3b98a0166f7b7196eba2ad518174d1a77165166d

* Empty strings are now direct constructed as `std::string()`, not as empty string literals.
* `startsWith` and `endsWith` no longer construct new a string. This should be an improvement
for libstdc++ when using older standards, as it doesn't use SSO but COW and thus even short
strings are expensive to first create.
* Various places now use char literal instead of string literals containing single char.
** `startsWith` and `endsWith` now also have overload that takes single char.

Generally the performance improvements under VS2015 are small, as going from short string
to char is mostly meaningless because of SSO (Catch doesn't push string handling that hard)
and previous commit removed most string handling if tests pass, which is the expect case.





* Empty strings are now direct constructed as `std::string()`, not as empty string literals.
* `startsWith` and `endsWith` no longer construct new a string. This should be an improvement
for libstdc++ when using older standards, as it doesn't use SSO but COW and thus even short
strings are expensive to first create.
* Various places now use char literal instead of string literals containing single char.
** `startsWith` and `endsWith` now also have overload that takes single char.

Generally the performance improvements under VS2015 are small, as going from short string
to char is mostly meaningless because of SSO (Catch doesn't push string handling that hard)
and previous commit removed most string handling if tests pass, which is the expect case.







Do not encode extended ASCII characters in XML reporter
2016-12-26T11:39:19+00:00

Igor Akhmetov

2016-12-26T11:39:19+00:00

8d16d95a995708d52f5ab19c0124b197eb4b7210












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