step-security/Cucumber Report to Annotations
This GitHub Action parses Cucumber test reports (JSON or NDJSON) and publishes them as GitHub Annotations—making test feedback visible directly in pull requests and commits
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| access-token | GitHub token used to post annotations | yes | ${{ github.token }} |
| path | Glob pattern to locate Cucumber JSON or NDJSON report files | yes | **/cucumber-report.json |
| check-status-on-error | Check conclusion when errors are found. Can be 'success', 'neutral', or 'failure'. | yes | failure |
| check-status-on-undefined | Check conclusion when undefined steps are found. Can be 'success', 'neutral', or 'failure'. | yes | success |
| check-status-on-pending | Check conclusion when pending steps are found. Can be 'success', 'neutral', or 'failure'. | yes | success |
| annotation-status-on-error | Annotation level for errors. Can be 'notice', 'warning', or 'failure'. | yes | failure |
| annotation-status-on-undefined | Annotation level for undefined steps. Can be 'notice', 'warning', or 'failure'. If unset, no annotation is generated for undefined steps. | no | — |
| annotation-status-on-pending | Annotation level for pending steps. Can be 'notice', 'warning', or 'failure'. If unset, no annotation is generated for pending steps. | no | — |
| show-number-of-error-on-check-title | If true, the number of errors will be shown in the check run title. | yes | true |
| show-global-summary-report | If true, includes a summary report for each feature file. | yes | false |
| number-of-test-error-to-fail-job | Minimum number of test errors required to fail the job. Use -1 to never fail the build. | yes | -1 |
| name | Name of the GitHub Check run | yes | Cucumber report |
Outputs
no outputs