Skip to content

Support "error" failures; add Github Actions outputs #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

jcourteau
Copy link
Contributor

@jcourteau jcourteau commented Aug 24, 2022

Bazel generates JUnit-like output, but it uses the error key instead of failure. It also does some other silly things with test aggregation, but I didn't dive into that with this PR.

Also added some Github Actions outputs.

Changes:

  • support the testsuites.testsuite[].testcase[].error XML node in addition to testsuites.testsuite[].testcase[].failure
  • add Github Actions outputs for passed/failed/skipped/total tests
  • added other outstanding features to the README
    • added the fact that the default output is now job summary
    • added docs for show
  • added docs for new outputs
  • added a Bazel Junit test output file
  • added test coverage for the above

Bazel generates JUnit-like output, but it uses the `error` key instead
of `failure`.

Also added some Github outputs; this can be useful in other actions.
* added other outstanding features to the README
  * added the fact that the default output is now job summary
  * added docs for show
* added docs for new outputs
* added a Bazel Junit test output file
* added test coverage for the above
@jcourteau jcourteau changed the title Support error and add outputs Support "error" failures; add Github Actions outputs Aug 24, 2022
@mbien
Copy link

mbien commented Oct 11, 2022

this would fix the issue I filed: #9

webknjaz and others added 5 commits November 7, 2022 09:19
NodeJS v12 is EOL and it's been deprecated since April 2022. It will
stop being available in GitHub Actions CI/CD workflows by the summer
2023. But it already triggers deprecation warnings that show up on the
workflow summary page:
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

This patch fixes that.

Resolves test-summary#15
Update README to point to v2
* actions/core - setOutput has changed under the hood; pre-1.10 versions
  are deprecated
* mocha - resolve a "high" vulnerability in a dependency
@jcourteau
Copy link
Contributor Author

Updated the PR:

  • rebased off of the latest changes
  • bump actions/core to 1.10; setOutput in the previous versions is deprecated
  • bump mocha to resolve a "high" risk vulnerability in a dependency, as reported by NPM.

@fpfaff
Copy link

fpfaff commented Nov 26, 2022

any update on this? The bump of actions/core to the latest version would be nice to get rid of GitHub's warnings when using this action.

Comment on lines +122 to +123
core.setOutput('total', total.counts.passed + total.counts.failed + total.counts.skipped)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
core.setOutput('total', total.counts.passed + total.counts.failed + total.counts.skipped)
core.setOutput('total', total.counts.passed + total.counts.failed + total.counts.skipped)

@ethomson
Copy link
Member

Thanks @jcourteau -- merged!

@ethomson ethomson closed this Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants