mirror of
https://github.com/catchorg/Catch2.git
synced 2024-11-22 21:36:11 +01:00
e340ab8db6
* Units from <ratio> are no longer redeclared in our own namespace * The default clock is `steady_clock`, not `high_resolution_clock`, because, as HH says "high_resolution_clock is useless. If you want measure the passing of time, use steady_clock. If you want user friendly time, use system_clock". * Benchmarking support is opt-in, not opt-out, to avoid the large (~10%) compile time penalty. * Benchmarking-related options in CLI are always present, to decrease the amount of code that is only compiled conditionally and making the whole shebang more maintainble. |
||
|---|---|---|
| .. | ||
| assertions.md | ||
| benchmarks.md | ||
| ci-and-misc.md | ||
| cmake-integration.md | ||
| command-line.md | ||
| commercial-users.md | ||
| configuration.md | ||
| contributing.md | ||
| deprecations.md | ||
| event-listeners.md | ||
| generators.md | ||
| limitations.md | ||
| list-of-examples.md | ||
| logging.md | ||
| matchers.md | ||
| opensource-users.md | ||
| other-macros.md | ||
| own-main.md | ||
| Readme.md | ||
| release-notes.md | ||
| release-process.md | ||
| reporters.md | ||
| slow-compiles.md | ||
| test-cases-and-sections.md | ||
| test-fixtures.md | ||
| tostring.md | ||
| tutorial.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
- Logging macros
- Test cases and sections
- Test fixtures
- Reporters
- Event Listeners
- Data Generators
- Other macros
Fine tuning:
Running:
Odds and ends:
FAQ:
Other: