mirror of
https://github.com/catchorg/Catch2.git
synced 2024-11-05 05:39:53 +01:00
aad926baf8
Introducing a new DISCOVERY_MODE mode option, which provides greater control over when catch_discover_tests perforsm test discovery. It has two supported modes: * POST_BUILD: The default behavior, which adds a POST_BUILD command to perform test discovery after the test has been built as was always done so far. * PRE_TEST: New mode, which delays test discovery until test execution. The generated include file generates the appropriate CTest files at runtime and regenerates the CTest files when the executable is updated. This mode can be used in build-environments that don't allow for executing the linked binaries at build-time (like in a cross-compilation environment). DISCOVERY_MODE can be controlled in two ways: 1. Setting the DISCOVERY_MODE when calling catch_discover_tests. 2. Setting the global CMAKE_CATCH_DISCOVER_TESTS_DISCOVERY_MODE prior to calling gtest_discover_tests. Closes #2493 |
||
---|---|---|
.. | ||
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-passing-failing.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
- Explicitly skipping, passing, and failing 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: