-
Notifications
You must be signed in to change notification settings - Fork 183
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
[Enhancement] Test Command enhanced reporters (JSON/YAML) #447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test reporters
joshfried-aws
requested review from
akshayrane,
setttings,
razcloud,
Brianwithay21,
wkexiang,
brianlaoaws,
reza-aws and
rpdutt
January 23, 2024 21:49
akshayrane
approved these changes
Jan 24, 2024
minhphuong98
approved these changes
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
#265
Description of changes:
This PR adds new enhanced reporting mechanisms to the test command. Similar to what we currently support with the validate command, users can now specify they want their output to be formatted in plaintext (single-line-summary), or a structured format (JSON/YAML).
This option is specified by either using the
--output-format
flag or-o
and then specifying any one of the 3 current supporting reporting mechanisms. The default behaviour will be single-line-summary to stay consistent with previous behaviour.Please note: similar to when using
structured
reporting mechanisms with the validate command, the test command does not allow for any plaintext to be output if the format is specified to be either JSON or YAML. This means if a user specifies the verbose flag and sets the output format to be either JSON or YAML, the program will error out alerting the user of the issue.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license