catch3/projects/SelfTest/MiscTests.cpp, branch v1.8.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Moved matchers tests into their own file 2017-02-21T14:19:09+00:00 Phil Nash 2017-02-21T14:19:09+00:00 4e6938d78e375d9bc3481d7baccb0f84341a4010 






Removed test for invoking String Matcher with NULL (this will no longer be supported)
2017-02-14T09:16:54+00:00

Phil Nash

2017-02-08T15:20:39+00:00

5530303be762d10c2c6e96f51a1465b57971eabe












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







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







Marked tests that use C++11 features with [c++11] tag and exclude them from approval tests
2017-01-09T14:37:28+00:00

Phil Nash

2017-01-09T14:26:59+00:00

1ae84897d4bd691420b0b8eb17b92cb62afbaf58












-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







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







Fixed !shouldfail
2016-03-14T19:13:34+00:00

Phil Nash

2016-03-14T19:13:34+00:00

447f53e9e3804e4baaafb61856b65984962ce1b8












Fixed test names mentioning the new Matcher combinator operators
2015-11-06T18:07:28+00:00

Phil Nash

2015-11-06T06:54:15+00:00

71fd2c2fdf3297b785fee4f3dead7b7412a2eac2