<feed xmlns='http://www.w3.org/2005/Atom'>
<title>catch3/src/catch2/reporters/catch_reporter_compact.cpp, branch constexpr_approx</title>
<subtitle>Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/'/>
<entry>
<title>Always default empty destructors</title>
<updated>2023-08-05T16:21:38+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2023-08-05T16:21:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=b593be21160766291bfef7ccb8b1471a4a64abd9'/>
<id>b593be21160766291bfef7ccb8b1471a4a64abd9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Some template instantiation reductions</title>
<updated>2023-05-01T11:21:45+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2023-04-29T12:29:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=10f0a5864319c0baa5c4cecb5e6138fd0c78a3e7'/>
<id>10f0a5864319c0baa5c4cecb5e6138fd0c78a3e7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Cleanup unneeded allocations from reporters</title>
<updated>2023-01-30T14:30:36+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2023-01-30T11:35:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=388f7e1737efd06bec03c0eb8c83253c461ec916'/>
<id>388f7e1737efd06bec03c0eb8c83253c461ec916</id>
<content type='text'>
The CompactReporter changes save 21 (430764 -&gt; 430743) allocations
when running the SelfTest binary in default configuration. They
save about 500 allocations when running the binary with `-s`.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The CompactReporter changes save 21 (430764 -&gt; 430743) allocations
when running the SelfTest binary in default configuration. They
save about 500 allocations when running the binary with `-s`.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add new SKIP macro for skipping tests at runtime (#2360)</title>
<updated>2023-01-12T14:01:47+00:00</updated>
<author>
<name>Philip Salzmann</name>
</author>
<published>2023-01-12T14:01:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=d548be26e3c54abc7e0b076319057d334e3ac589'/>
<id>d548be26e3c54abc7e0b076319057d334e3ac589</id>
<content type='text'>
* Add new SKIP macro for skipping tests at runtime

This adds a new `SKIP` macro for dynamically skipping tests at runtime.
The "skipped" status of a test case is treated as a first-class citizen,
like "succeeded" or "failed", and is reported with a new color on the
console.

* Don't show "skipped assertions" in console/compact reporters

Also extend skip tests to cover a few more use cases.

* Return exit code 4 if all test cases are skipped

* Use LightGrey for the skip colour

This isn't great, but is better than the deep blue that was borderline
invisible on dark backgrounds. The fix is to redo the colouring
a bit, including introducing light-blue that is actually visible.

* Add support for explicit skips in all reporters

* --allow-running-no-tests also allows all tests to be skipped

* Add docs for SKIP macro, deprecate IEventListener::skipTest

Co-authored-by: Martin Hořeňovský &lt;martin.horenovsky@gmail.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Add new SKIP macro for skipping tests at runtime

This adds a new `SKIP` macro for dynamically skipping tests at runtime.
The "skipped" status of a test case is treated as a first-class citizen,
like "succeeded" or "failed", and is reported with a new color on the
console.

* Don't show "skipped assertions" in console/compact reporters

Also extend skip tests to cover a few more use cases.

* Return exit code 4 if all test cases are skipped

* Use LightGrey for the skip colour

This isn't great, but is better than the deep blue that was borderline
invisible on dark backgrounds. The fix is to redo the colouring
a bit, including introducing light-blue that is actually visible.

* Add support for explicit skips in all reporters

* --allow-running-no-tests also allows all tests to be skipped

* Add docs for SKIP macro, deprecate IEventListener::skipTest

Co-authored-by: Martin Hořeňovský &lt;martin.horenovsky@gmail.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>Fix references to license file</title>
<updated>2022-10-28T09:30:15+00:00</updated>
<author>
<name>Lars Toenning</name>
</author>
<published>2022-10-28T09:22:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=f1084fb30990fe40c8f5b70034970c7eb4e1da72'/>
<id>f1084fb30990fe40c8f5b70034970c7eb4e1da72</id>
<content type='text'>
The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1
</pre>
</div>
</content>
</entry>
<entry>
<title>Change reporters to report filters in round-trippable format</title>
<updated>2022-10-27T18:46:59+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2022-10-27T18:43:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=d41da10c549f13d5d0d0fe54300c5f1d9f2082d9'/>
<id>d41da10c549f13d5d0d0fe54300c5f1d9f2082d9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Use console reporter's totals summary for compact reporter</title>
<updated>2022-10-25T18:02:26+00:00</updated>
<author>
<name>Philip Salzmann</name>
</author>
<published>2022-10-24T12:17:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=6185d0cc0a737d5a009f626d3611b868512d12f7'/>
<id>6185d0cc0a737d5a009f626d3611b868512d12f7</id>
<content type='text'>
This changes the compact reporter's summary of test run totals to use
the same format as the console reporter. This means that while output is
no longer on a single line (two instead), it now includes totals for
`failedButOk` test cases and assertions, which were previously missing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This changes the compact reporter's summary of test run totals to use
the same format as the console reporter. This means that while output is
no longer on a single line (two instead), it now includes totals for
`failedButOk` test cases and assertions, which were previously missing.
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow easy retrieval of RNG seed by the users</title>
<updated>2022-08-18T21:23:18+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2022-08-18T19:22:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=dc001fa935d71b4b77f263fce405c9dbdfcbfe28'/>
<id>dc001fa935d71b4b77f263fce405c9dbdfcbfe28</id>
<content type='text'>
This makes it so that they don't need parallel RNG seed passing
infrastructure for randomized data generation (e.g. inputs for
benchmarks).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This makes it so that they don't need parallel RNG seed passing
infrastructure for randomized data generation (e.g. inputs for
benchmarks).
</pre>
</div>
</content>
</entry>
<entry>
<title>Always report rng seed from builtin reporters</title>
<updated>2022-04-19T08:32:13+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2022-04-19T08:32:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=17a04f88d90d3687bd561e89dab40e4ba6a55b83'/>
<id>17a04f88d90d3687bd561e89dab40e4ba6a55b83</id>
<content type='text'>
Not all reporters use a format that supports this, so TeamCity
and Automake reporters still do not report it. The console
reporter now reports it even on successful runs, where before
it only reported the rng seed in the header, which was showed
either for failed run, or for run with `-s`.

CLoses #2065
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Not all reporters use a format that supports this, so TeamCity
and Automake reporters still do not report it. The console
reporter now reports it even on successful runs, where before
it only reported the rng seed in the header, which was showed
either for failed run, or for run with `-s`.

CLoses #2065
</pre>
</div>
</content>
</entry>
<entry>
<title>ColourGuard is no longer constructed engaged</title>
<updated>2022-03-24T15:02:54+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2022-03-21T22:20:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=081a1e9abaf32a759fd08a01fcf7a65860f91a63'/>
<id>081a1e9abaf32a759fd08a01fcf7a65860f91a63</id>
<content type='text'>
Forcing it to be engaged explicitly, either via `op&lt;&lt;`, or by
`ColourGuard::engage`, fixes an issue with multiple `ColourGuard`s
being constructed in a single expression. Because the construction
of the `ColourGuard` instances can happen in arbitrary order,
colours would be applied in arbitrary order too. However, a chain
of `op&lt;&lt;`s has strict call orders, fixing this issue.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Forcing it to be engaged explicitly, either via `op&lt;&lt;`, or by
`ColourGuard::engage`, fixes an issue with multiple `ColourGuard`s
being constructed in a single expression. Because the construction
of the `ColourGuard` instances can happen in arbitrary order,
colours would be applied in arbitrary order too. However, a chain
of `op&lt;&lt;`s has strict call orders, fixing this issue.
</pre>
</div>
</content>
</entry>
</feed>
