catch3/tests/TestScripts, branch v3.0.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Always report rng seed from builtin reporters 2022-04-19T08:32:13+00:00 Martin Hořeňovský 2022-04-19T08:32:13+00:00 17a04f88d90d3687bd561e89dab40e4ba6a55b83 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 
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
Add default reporter for Bazel integration (#2399) 2022-04-08T16:01:59+00:00 Lukasz Okraszewski 2022-04-08T16:01:59+00:00 cb551b4f6d338020322eb39a2f3747c81896a1ba When the added Bazel configuration flag is enabled, a default JUnit reporter will be added if the XML envrioment variable is defined. Fix include paths for generated config header. Enable Bazel config by default when building with Bazel. Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com> 
When the added Bazel configuration flag is enabled,
a default JUnit reporter will be added if the XML
envrioment variable is defined.
Fix include paths for generated config header.
Enable Bazel config by default when building with
Bazel.


Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
 Add tests for CMake configure toggles passing to Catch2 build 2022-02-20T18:32:30+00:00 Martin Hořeňovský 2022-02-19T20:27:53+00:00 72f037266415fee521adc598bd324fea8001cd77 






Use the new licence header in TestScripts
2022-01-28T23:04:49+00:00

Martin Hořeňovský

2022-01-28T23:04:49+00:00

51888d360ab6c21a704d0ba9c66da1b55751940a












Handle full unique test identifiers in testRandomOrder.py
2022-01-27T20:11:37+00:00

Martin Hořeňovský

2022-01-27T17:57:48+00:00

d861e73f86a7c6c7482337e4194d8f9f3ce1f00e












Make testSharding.py test script executable
2021-10-27T15:24:30+00:00

Martin Hořeňovský

2021-10-27T12:51:45+00:00

ec2d5013fbeddd30e65c44639287b15eb591d68e












Cleanup the shard integration test script
2021-10-27T15:24:30+00:00

Martin Hořeňovský

2021-10-27T12:26:07+00:00

342ef5ca7eb7df0ee02dfa01714b6391cdbe87bc












Allow test sharding for e.g. Bazel test sharding feature
2021-10-27T15:24:30+00:00

Ben Dunkin

2021-07-11T19:46:05+00:00

3087e19cc72ccb6caddc42ec2f39eebc56160754

This greatly simplifies running Catch2 tests in single binary
in parallel from external test runners. Instead of having to
shard the tests by tags/test names, an external test runner
can now just ask for test shard 2 (out of X), and execute that
in single process, without having to know what tests are actually
in the shard.

Note that sharding also applies to test listing, and happens after
tests were ordered according to the `--order` feature.





This greatly simplifies running Catch2 tests in single binary
in parallel from external test runners. Instead of having to
shard the tests by tags/test names, an external test runner
can now just ask for test shard 2 (out of X), and execute that
in single process, without having to know what tests are actually
in the shard.

Note that sharding also applies to test listing, and happens after
tests were ordered according to the `--order` feature.







Add new reporter event called for each test case enter/exit
2021-09-14T11:19:45+00:00

Martin Hořeňovský

2021-09-11T22:00:47+00:00

10fb93cce8cb878fdfe8faa118b531258db96a26

This means that e.g. for `TEST_CASE` with two sibling `SECTION`s
the event will fire twice, because the `TEST_CASE` will be entered
twice.

Closes #2107 (the event mentioned there already exists, but this
is its counterpart that we also want to provide to users)





This means that e.g. for `TEST_CASE` with two sibling `SECTION`s
the event will fire twice, because the `TEST_CASE` will be entered
twice.

Closes #2107 (the event mentioned there already exists, but this
is its counterpart that we also want to provide to users)







Fix how testRandomOrder.py builds tag arguments
2020-07-26T08:51:55+00:00

Martin Hořeňovský

2020-07-11T19:31:08+00:00

250d9b9c72219cc196e971356705af6fd24b6ed2