-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Output verbosity for test cases #11639
Copy link
Copy link
Closed
Labels
topic: configrelated to config handling, argument parsing and config filerelated to config handling, argument parsing and config filetopic: reportingrelated to terminal output and user-facing messages and errorsrelated to terminal output and user-facing messages and errorstype: proposalproposal for a new feature, often to gather opinions or design the API around the new featureproposal for a new feature, often to gather opinions or design the API around the new feature
Description
Activity
Metadata
Metadata
Assignees
Labels
topic: configrelated to config handling, argument parsing and config filerelated to config handling, argument parsing and config filetopic: reportingrelated to terminal output and user-facing messages and errorsrelated to terminal output and user-facing messages and errorstype: proposalproposal for a new feature, often to gather opinions or design the API around the new featureproposal for a new feature, often to gather opinions or design the API around the new feature
This is a follow on to fine-grained output verbosity for assertions (#11387/#11473). The next "category" that seems to stand out based on the current behavior is how
pytestdisplays test cases are it executes them. By this I mean the distinction between:--quietvs
default
vs
--verboseAdditionally, I think this would also extend to the output of
--collect-only(doesn't show all of the states):--quiet --quietvs
default
There doesn't seem to be an existing name for this, so I plan to start the work using
test_case. If someone comes up with a better name, I'd be happy to use that. I don't think there would be anything else that would fit into this "category". But feel free to bring things to my attention if I missed something.