Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Here is junit report feature.
--junit-xml
as cmd-line param or putjunit: yes
into global config filelogs/latest/report.xml
skipped
in report as wellHere is an example of how it can be displayed in run summary
https://github.com/man1207/SIPssert/actions/runs/12482574669/attempts/1#summary-34836934692
or in detailed
https://github.com/man1207/SIPssert/actions/runs/12482574669/job/34837079496
I don't include here commits related to actions/workflows. Only feature code.
If you wish to modify action and workflow to gain junit reports in SIPssert repo it can be performed such a way:
--junit-xml
cmd-line param when executesipssert
command in action.junit: yes
into global config file insipssert-opensips-tests
repositorymikepenz/action-junit-report
ordorny/test-reporter
for instance). You can call these actions fromsipssert-opensips-tests
repo by callingmikepenz/action-junit-report
per job anddorny/test-reporter
for run as a whole (you must aggregate reports from artifacts in such case).Or, if you wish, I can bring commits that generate reports in workflow run in yet another PR. Look at links above. Do you like how reports look in workflow run?