You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would like a way for this action to fail IF the test coverage % declines by a minimum percent
Description
Add option to fail action if test coverage % declines
Alternatives
Potentially easier / more general solution:
If there's a way to get a machine-parseable summary of test coverage (e.g. JSON), including the % changes, as an output variable, then a subsequent workflow step and can read/parse that output and do arbitrary logic to fail/pass the workflow.
^ Why not parse the output: 'report_markdown' output? Currently the 'report_markdown' option conflicts with the 'comment' option, which doesn't work for my use case because I want to have the comment added, and ALSO get the test coverage diff %. Also the markdown output is not a good format for further programmatic logic, so an output in JSON or something similar would be preferred.
The text was updated successfully, but these errors were encountered:
Can this be re-opened? This is an extremely valuable addition and a much better way to test coverage changed in a larger existing app than static thresholds (imo).
Idea
Would like a way for this action to fail IF the test coverage % declines by a minimum percent
Description
Add option to fail action if test coverage % declines
Alternatives
Potentially easier / more general solution:
If there's a way to get a machine-parseable summary of test coverage (e.g. JSON), including the % changes, as an output variable, then a subsequent workflow step and can read/parse that output and do arbitrary logic to fail/pass the workflow.
^ Why not parse the
output: 'report_markdown'
output? Currently the'report_markdown'
option conflicts with the'comment'
option, which doesn't work for my use case because I want to have the comment added, and ALSO get the test coverage diff %. Also the markdown output is not a good format for further programmatic logic, so an output in JSON or something similar would be preferred.The text was updated successfully, but these errors were encountered: