mirror of https://github.com/catchorg/Catch2.git
80b0d6975c
A test runner already has a --durations option to print durations. However, this isn't entirely satisfactory. When there are many tests, this produces output spam which makes it hard to find the test failure output. Nevertheless, it is helpful to be informed of tests which are unusually slow. Therefore, introduce a new option --min-duration that causes all durations above a certain threshold to be printed. This allows slow tests to be visible without mentioning every test. |
||
|---|---|---|
| .. | ||
| Readme.md | ||
| 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 | ||
| 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 | ||
Readme.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
- Micro benchmarking
Fine tuning:
Running:
Odds and ends:
FAQ:
Other: