Currently, when using the GitHubReporter, all test details (including passed, skipped, and failed) are output in the report. While this is helpful in some contexts, it can create quite a lot of noise, especially in larger projects where the majority of tests pass consistently.
Feature Request
It would be very helpful to have an option/configuration setting in the GitHubReporter that restricts detailed output to only Failed tests.
Rationale
- Improved readability: Developers and reviewers can focus directly on the failures without sifting through large amounts of successful test output.
- Cleaner reports: Makes the GitHub summary more concise, especially valuable in projects with thousands of tests.
- Optional behavior: Keeping it as a configuration option ensures flexibility – teams that want full visibility can keep it as is, while others can minimize verbosity.
Possible Implementation Ideas
- Add a flag such as
onlyShowFailed = true to the GitHubReporter options.
- Alternatively, extend the reporter with different verbosity levels (e.g.,
All, FailedOnly).
This feature would enhance usability for larger teams and CI pipelines by making reports more focused and efficient.
Thanks again for considering this request!
Currently, when using the GitHubReporter, all test details (including passed, skipped, and failed) are output in the report. While this is helpful in some contexts, it can create quite a lot of noise, especially in larger projects where the majority of tests pass consistently.
Feature Request
It would be very helpful to have an option/configuration setting in the
GitHubReporterthat restricts detailed output to onlyFailedtests.Rationale
Possible Implementation Ideas
onlyShowFailed = trueto theGitHubReporteroptions.All,FailedOnly).This feature would enhance usability for larger teams and CI pipelines by making reports more focused and efficient.
Thanks again for considering this request!