-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
junitxml make verbose output opt-in #595
Copy link
Copy link
Closed
Labels
good first issueeasy issue that is friendly to new contributoreasy issue that is friendly to new contributorstatus: help wanteddevelopers would like help from experts on this topicdevelopers would like help from experts on this topictype: 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
Metadata
Metadata
Assignees
Labels
good first issueeasy issue that is friendly to new contributoreasy issue that is friendly to new contributorstatus: help wanteddevelopers would like help from experts on this topicdevelopers would like help from experts on this topictype: 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
Originally reported by: David Szotten (BitBucket: davidszotten, GitHub: davidszotten)
6954363 changed junitxml to include captured output for passing and skipped tests in the output by default. this makes the xml unnecessarily large for our use cases
i think this behaviour should become opt-in (or at the very least add opt-out)
feature is easy to add, but my issue was with giving this a good option name. i was also slightly concerned with growing the already large list of options with parameters that only apply when already using --junitxml
are there any plans for grouping/namespacing options (so that a top level --help would be less verbose)
and setting aside the digression, any thoughts on making this opt-in (and if so, of a good option name. so far considered junitxml-verbose-output, junitxml-always-include-output; just using the --verbose flag (don't like that))
thanks