mirror of
https://github.com/catchorg/Catch2.git
synced 2024-11-05 05:39:53 +01:00
d548be26e3
* 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ý <martin.horenovsky@gmail.com> |
||
---|---|---|
.. | ||
assertions.md | ||
benchmarks.md | ||
ci-and-misc.md | ||
cmake-integration.md | ||
command-line.md | ||
commercial-users.md | ||
comparing-floating-point-numbers.md | ||
configuration.md | ||
contributing.md | ||
deprecations.md | ||
event-listeners.md | ||
faq.md | ||
generators.md | ||
limitations.md | ||
list-of-examples.md | ||
logging.md | ||
matchers.md | ||
migrate-v2-to-v3.md | ||
opensource-users.md | ||
other-macros.md | ||
own-main.md | ||
Readme.md | ||
release-notes.md | ||
release-process.md | ||
reporter-events.md | ||
reporters.md | ||
skipping.md | ||
test-cases-and-sections.md | ||
test-fixtures.md | ||
tostring.md | ||
tutorial.md | ||
usage-tips.md | ||
why-catch.md |
Reference
To get the most out of Catch2, start with the tutorial. Once you're up and running consider the following reference material.
Writing tests:
- Assertion macros
- Matchers (asserting complex properties)
- Comparing floating point numbers
- Logging macros
- Test cases and sections
- Test fixtures
- Skipping tests at runtime
- Reporters (output customization)
- Event Listeners
- Data Generators (value parameterized tests)
- Other macros
- Micro benchmarking
Fine tuning:
Running:
Odds and ends:
- Frequently Asked Questions (FAQ)
- Best practices and other tips
- CMake integration
- Tooling integration (CI, test runners, other)
- Known limitations
Other: