publish-unit-test-result-action
Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.
What publish-unit-test-result-action is
publish-unit-test-result-action is a GitHub Action that reads test result files and posts their results to GitHub. It reads JSON files from Dart and Mocha, TRX files from MSTest and Visual Studio, and JUnit, NUnit and XUnit XML files. It runs on Linux, macOS and Windows runners. The default variant uses Docker, while separate macOS, Windows and Linux variants run without Docker. It is added as a workflow step whose `files` input lists glob patterns for result files. By default the action itself does not fail when tests fail. The `action_fail` and `fail_on` options control failure behaviour. Its minimal job permissions are write access to checks and, unless comment_mode is off, write access to pull requests.
Written from the project's README, read .
- Category
- CI and reporting
- License
- Apache-2.0
- Language
- Python
- Changelog
- Releases on GitHub
Repository metrics
Status
activeLast commit within 90 days of the fetch date.Computed from the last commit date and the archive flag on the fetch date. See the status rules.
Alternatives
Listed CI and reporting tools, same primary language first, then by GitHub stars. Each line gives one fact from the tool's documentation where it differs from publish-unit-test-result-action's, with its source.
Coverage.py: Languages or inputs covered: Python code (CPython 3.10 to 3.15, PyPy3). source: README
Lighthouse CI: Languages or inputs covered: URLs, or HTML files in a static build directory (staticDistDir). source: Docs: Configuration
nyc: Languages or inputs covered: JavaScript (ES5, ES2015+); Babel and TypeScript through source maps. source: README
Allure Report: Languages or inputs covered: Result files written by framework integrations to the allure-results directory. source: Docs: How to generate a report
JaCoCo: Languages or inputs covered: Java code. source: README
gotestsum: Languages or inputs covered: Go test output (go test -json). source: README
c8: Languages or inputs covered: JavaScript run in Node.js through native V8 coverage; TypeScript and JSX through source maps. source: README
ReportPortal: Languages or inputs covered: Test results sent by framework agents; imported JUnit or Robot Framework XML files. source: Docs: Import data to ReportPortal
Questions
Is publish-unit-test-result-action open source?
Yes. publish-unit-test-result-action is released under Apache-2.0, an OSI-approved license, as reported by the GitHub API on 2026-09-22.
Is publish-unit-test-result-action maintained?
On 2026-09-22, the last commit to the default branch was on 2026-09-17, so the listed status is active. Rule: Last commit within 90 days of the fetch date.
How many GitHub stars does publish-unit-test-result-action have?
751 stars on 2026-09-22, from the GitHub API. The number is refreshed at each monthly update.
What language is publish-unit-test-result-action written in?
The repository's primary language, as reported by the GitHub API, is Python.
Sources
- GitHub REST API: repository, read
- GitHub REST API: commits, read
- GitHub REST API: latest release, read
- GitHub REST API: contributors, read
- README, read