catch3/include/reporters, branch v2.11.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Different approach to proper colouring of filters 2020-03-19T10:08:01+00:00 Martin Hořeňovský 2020-02-15T20:18:56+00:00 5561d0342dfbfb6882361aeb519bbdfb49fa6eb8 






Switch back to uncolored output after printing filters
2020-03-19T10:08:01+00:00

Till Hofmann

2020-02-10T13:52:35+00:00

3a15315a37c16a5cebee30788a19023f85b9f401

After printing the list of filters, switch back from yellow to black
before printing a newline to avoid the remaining output to be colored in
yellow.





After printing the list of filters, switch back from yellow to black
before printing a newline to avoid the remaining output to be colored in
yellow.







Don't cast nanoseconds to integers when writing output
2020-03-08T11:10:44+00:00

khyperia

2020-02-26T14:32:34+00:00

022b61ff9218b427831a182b8df929fde36a20eb












Some refactorings:
2020-01-25T08:01:04+00:00

offa

2020-01-21T20:04:42+00:00

2d172dc688ffab0867a94928159e93384475a870

 - Overrides added
 - usages of push_back() replaced with emplace_back()
 - Loop variable made const-refernce
 - NULL replaced with nullptr
 - Names used in the declaration and definition unified
 - size() replaced with empty
 - Identical cases merged





 - Overrides added
 - usages of push_back() replaced with emplace_back()
 - Loop variable made const-refernce
 - NULL replaced with nullptr
 - Names used in the declaration and definition unified
 - size() replaced with empty
 - Identical cases merged







Refactored XMLWriter to provide finer-grained control over formatting
2019-10-29T12:59:18+00:00

Martin Hořeňovský

2019-06-22T12:39:34+00:00

3136c4fb6aeba965f0a6700eff60fa29d9b8c326












Improve JUnit failure report
2019-10-27T17:02:14+00:00

Alexander Stein

2019-08-07T20:39:01+00:00

2fbd66c51cbf3a406dc6bb8ddc6b9a0b96077a72

The JUnit report is improved in that:
* The message shows the testing condition, not the result
* The actual message has similar output than the console one





The JUnit report is improved in that:
* The message shows the testing condition, not the result
* The actual message has similar output than the console one







Add SonarQube Generic Test Data reporter
2019-10-27T09:02:41+00:00

sp-dani-garcia

2019-08-29T15:47:56+00:00

51b29ced1ac2bde83d977283f6e0b4f871898b8a

It outputs reports in the `Generic Execution Test Data` format, see
https://docs.sonarqube.org/latest/analysis/generic-test/, specifically
https://docs.sonarqube.org/latest/analysis/generic-test/#header-2

Close #1738 (this is a cherry-pick and fixup of that PR)





It outputs reports in the `Generic Execution Test Data` format, see
https://docs.sonarqube.org/latest/analysis/generic-test/, specifically
https://docs.sonarqube.org/latest/analysis/generic-test/#header-2

Close #1738 (this is a cherry-pick and fixup of that PR)







Fixes #1766: Catch terminates when parsing invalid test name
2019-10-19T19:14:06+00:00

amitherman95

2019-10-19T13:50:46+00:00

84856844e17f78e9f3a9f113df9d3ff23aad69e1












Simplified benchmark output with --benchmark-no-analysis
2019-10-07T13:40:00+00:00

RT222

2019-10-07T13:40:00+00:00

2331249a8d7a982aead69ef8d1193446953e8865

Removed unused informations from benchmarks output when the --benchmark-no-analysis flag is used, making the results easier to read.




Removed unused informations from benchmarks output when the --benchmark-no-analysis flag is used, making the results easier to read.






Inline SourceLineInfo::empty definition
2019-09-08T16:20:49+00:00

Martin Hořeňovský

2019-09-08T16:20:49+00:00

293012a002ef5351adbfcc0cbf7cdfdc93aed115