[Enhancement] Output reports in a standard format

[benbridts]

Is your feature request related to a problem? Please describe.

When using Guard as part of a CI/CD pipeline, I would like to use my current reporting tool to track rule failures and success over time and use my tools integrations (ie links to files and lines) to easily navigate through source code

Describe the solution you'd like

There are multiple popular report file outputs (CodeBuild supports 6 different ones), picking one or two from that list and adding a --report option would be great.

Additional context

I don't think this should replace the current output formats (I might want single-line output for my build log in addition to the report). A --output none option might be useful, but > /dev/null would work in a lot of environments too.

[razcloud]

Thanks for bringing this up @benbridts

Curious, any votes on which option will support your use case best? JUnit? Cucumber JSON? etc?

[drmmarsunited]

I'm happy to open another issue for this, but I came here with the same ask specifically around getting some kind of output from the test command. For my particular use case, parity with the output formats from the validation command would be a great start (mostly JSON), followed closely by JUnit.

[benbridts]

For my use case any output that is supported by CodeBuild would be great

[razcloud]

Thank you @benbridts Will take this back to the team.

@drmmarsunited Noted.

[fabiodouek]

+1 on this one. Any test report format supported by CodeBuild would be great.
My personal preference is JUnit as it seems to be supported by most tools.

[andrew-glenn]

Related: Add support for SARIF [Enhancement] #412

[joshfried-aws]

Hi @benbridts, @drmmarsunited and @fabiodouek just wanted to let the 3 of you know that we now have support for JSON/YAML/JUnit reporters for both test and validate command

I am going to go ahead and close out this issue.

Feel free to reopen if necessary