Repository navigation
ci(test): report bats results with the shared test-report action - #215
DevSecNinja wants to merge 5 commits into
Conversation
Replace the third-party JUnit reporter with the shared test-report action and drop checks: write. Refs #214
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the CI test-reporting change.
No open issues 🎉
What changed in this PR
This PR trials the shared test-report action for Bats results in the infrastructure CI workflow, addressing #214.
Changes:
- Replaces
mikepenz/action-junit-reportwith the shared action for job summaries and error annotations. - Removes the unused
checks: writepermission while preserving the XML artifact upload. - Pins the trial action to a commit, with a released commit pin planned before merging.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Switches test reporters and removes the old reporter’s write permission. |
Review effort: Balanced

Trial of the shared
test-reportaction from DevSecNinja/.github#604.mikepenz/action-junit-reportstep withDevSecNinja/.github/actions/test-report, which writes the bats results to the job summary (counts per suite plus a table of failed tests) and adds::errorannotations on the failing lines. It uses standard-library Python only.checks: write, which only the old reporter needed.tests/bash/run-tests.sh: underset -e, a failingbatsexited beforereport.xmlwas renamed totest-results.xml, so failed runs never had a report. That affected the old reporter too. The script still exits with bats' exit code.test-results.xmlartifact upload.Trial runs:
tests/bash/report-trial.bats:6.The action is pinned to the reviewed head of DevSecNinja/.github#604 for this trial. Before merging, I'll repin it to the released commit SHA with a version comment.
Closes #214