New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Argument --verbosity is not intuitive #2439
Comments
Preliminary addition to documentation: I could not document |
After some investigation, you are right in that verbosity is currently only taken into account by the listings. However, it is also meant for reporters if they can meaningfully support it. Most of the custom reporters are meant to be machine-friendly, so it is likely meaningless for them, but e.g. the Console reporter could support different verbosities... if someone bothers to add them (I probably won't, as the effort to do so isn't worth it for me). nitpick on the docs: You should mention that this is for the default listing implementation, and I think that the normal (default) verbosity should be the one with docs, and the other ones should be documented as diffs from the normal. (So normal shouldn't be "same as quiet", but quiet should be "same as normal".) |
No nitpicking, it is a good suggestion. I have this now: Do you think I should create a PR and move discussion over there? |
Opening up a new PR would be better, yes. |
Description
--verbosity in Catch2 applications has a different behaviour than usually expected.
Preferably the option could be renamed to something like "level of detail" (and "quiet" replaced with "low"), as an alias not to break the interface. At least the help string should be changed to something like "set the level of detail for the --list-* options".
Additional context
--list-test-names-only was removed in #1190
The text was updated successfully, but these errors were encountered: