Publish results as job summary #266
Conversation
![sonatype-lift[bot]](https://avatars.githubusercontent.com/in/9843?s=60&v=4){kind=small}
|
Well, I think pretty much all comments have been covered 😌 |
|
PR #267 is merged, please rebase and I will review again tomorrow. |
This comment has been minimized.
This comment has been minimized.
Unit Test Results (Test Files) 26 files ±0 4 errors 23 suites ±0 39m 21s ⏱️ ±0s For more details on these parsing errors, failures and errors, see this check. Results for commit e5bc065. ± Comparison against base commit b406f72. ♻️ This comment has been updated with latest results. |
|
Look at this (scroll down to the job summaries): https://github.com/EnricoMi/publish-unit-test-result-action/actions/runs/2306018943 |
|
What about this markdown for the job summary (reference comment and check)? Currently: 4 parse errors, 6 errors, 25 fail, 20 skipped, 228 pass in 39m 21s 26 files 4 errors 23 suites 39m 21s ⏱️ Results for commit 9eac4d8. With title and one-line summary: Unit Test Results (Test Files)4 parse errors, 6 errors, 25 fail, 20 skipped, 228 pass in 39m 21s 26 files 4 errors 23 suites 39m 21s ⏱️ Results for commit 9eac4d8. Like the comment, not the check: Unit Test Results (Test Files) 26 files 4 errors 23 suites 39m 21s ⏱️ Results for commit 9eac4d8. |
|
Which one do you prefer? I assume it's about not passing the title to get to the last one (my personal favorite) |
|
Yes, I prefer that one too. |
|
Thanks for the contribution! |
|
As those environment files are a GitHub Actions feature, I have added them to I am going to migrate |
|
This has been released, enjoy! |
Fixes #264
I took the liberty of enhancing the tests to use absolute paths for files, it's easier to run tests in my IDE.