actions-marketplace-validations/Publish Test Results

Publishes JUnit, NUnit, XUnit, TRX, JSON test results on GitHub for .NET, Dart, Java, JS, Jest, Mocha, Python, Scala, …

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Mar 1, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/enricomi_publish-unit-test-result-action@f3a4c8ee80460c780d2932e55fb914138ecaca2c # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
github_token	GitHub API Access Token.	no	${{ github.token }}
github_token_actor	[deprecated] This is not needed any more as this is detected automatically.	no	—
github_retries	Requests to the GitHub API are retried this number of times. The value must be a positive integer or zero.	no	10
ssl_verify	Either "true" or "false", in which case it controls whether to verify the Github server’s TLS certificate, or a string, in which case it must be a path to a CA bundle to use. Default is "true".	no	true
commit	Commit SHA to which test results are published. Only needed if the value of GITHUB_SHA does not work for you.	no	—
check_name	Name of the created check run.	no	Test Results
comment_title	An alternative title for the pull request comment. Defaults to value of check_name input.	no	—
comment_mode	The action posts comments to pull requests that are associated with the commit. Set to "always" - always comment, "changes" - comment when changes w.r.t. the target branch exist, "changes in failures" - when changes in the number of failures and errors exist, "changes in errors" - when changes in the number of (only) errors exist, "failures" - when failures or errors exist, "errors" - when (only) errors exist, "off" - to not create pull request comments.	no	always
fail_on	The created test result check run has failure state if any test fails or test errors occur. Never fails when set to "nothing", fails only on errors when set to "errors". Default is "test failures".	no	test failures
action_fail	When set "true", the action itself fails when tests have failed (see option fail_on).	no	false
action_fail_on_inconclusive	When set "true", the action itself fails when tests are inconclusive (no test results).	no	false
files	File patterns of test result files. Relative paths are known to work best, while the non-Docker action also works with absolute paths. Supports "", "*", "?", and "[]" character ranges. Use multiline string for multiple patterns. Patterns starting with "!" exclude the matching files. There have to be at least one pattern starting without a "!".	no	—
junit_files	Deprecated, use "files" option instead.	no	—
nunit_files	Deprecated, use "files" option instead.	no	—
xunit_files	Deprecated, use "files" option instead.	no	—
trx_files	Deprecated, use "files" option instead.	no	—
time_unit	Time values in the test result files have this unit. Supports "seconds" and "milliseconds".	no	seconds
test_file_prefix	Paths in the test result files should be relative to the git repository for annotations to work best. This prefix is added to (if starting with "+"), or remove from (if starting with "-") test file paths. Examples: "+src/" or "-/opt/actions-runner".	no	—
report_individual_runs	Individual runs of the same test may see different failures. Reports all individual failures when set "true" or the first only otherwise.	no	—
report_suite_logs	In addition to reporting regular test logs, also report test suite logs. These are logs provided on suite level, not individual test level. Set to "info" for normal output, "error" for error output, "any" for both, or "none" for no suite logs at all. Defaults to "none".	no	none
deduplicate_classes_by_file_name	De-duplicates classes with same name by their file name when set "true", combines test results for those classes otherwise.	no	—
large_files	Support for large files is enabled when set to "true". Defaults to "false", unless ignore_runs is "true".	no	—
ignore_runs	Does not collect test run information from the test result files, which is useful for very large files. This disables any check run annotations.	no	false
check_run	Set to "true", the results are published as a check run, but it may not be associated with the workflow that ran this action.	no	true
job_summary	Set to "true", the results are published as part of the job summary page of the workflow run.	no	true
compare_to_earlier_commit	Test results are compared to results of earlier commits to highlight changes: "false" - disable comparison, "true" - compare across commits.	no	true
pull_request_build	As part of pull requests, GitHub builds a merge commit, which combines the commit and the target branch. If tests ran on the actual pushed commit, then set this to "commit". Defaults to "merge".	no	merge
event_file	An alternative event file to use. Useful to replace a "workflow_run" event file with the actual source event file.	no	—
event_name	An alternative event name to use. Useful to replace a "workflow_run" event name with the actual source event name: github.event.workflow_run.event.	no	—
test_changes_limit	Limits the number of removed or skipped tests reported on pull request comments. This report can be disabled with a value of 0. The default is 10.	no	—
check_run_annotations	Adds additional information to the check run. This is a comma-separated list of any of the following values: "all tests" - list all found tests, "skipped tests" - list all skipped tests. Set to "none" to add no extra annotations at all.	no	all tests, skipped tests
check_run_annotations_branch	Adds check run annotations only on given branches. Comma-separated list of branch names allowed, asterisk "*" matches all branches. Defaults to event.repository.default_branch or "main, master".	no	—
seconds_between_github_reads	Sets the number of seconds the action waits between concurrent read requests to the GitHub API. This throttles the API usage to avoid abuse rate limits: https://docs.github.com/en/rest/overview/resources-in-the-rest-api#abuse-rate-limits.	no	0.25
seconds_between_github_writes	Sets the number of seconds the action waits between concurrent write requests to the GitHub API. This throttles the API usage to avoid abuse rate limits: https://docs.github.com/en/rest/overview/resources-in-the-rest-api#abuse-rate-limits.	no	2.0
secondary_rate_limit_wait_seconds	Sets the number of seconds to wait before retrying secondary rate limit errors. If not set, the default defined in the PyGithub library is used (currently 60 seconds).	no	—
json_file	Results are written to this JSON file.	no	—
json_thousands_separator	Formatted numbers in JSON use this character to separate groups of thousands. Common values are "," or ".". Defaults to punctuation space (\u2008).	no	��
json_suite_details	Write out all suite details to the JSON file. Setting this to "true" can greatly increase the size of the output. Defaults to "false".	no	false
json_test_case_results	Write out all individual test case results to the JSON file. Setting this to "true" can greatly increase the size of the output. Defaults to "false".	no	false
search_pull_requests	Prior to v2.6.0, the action used the "/search/issues" REST API to find pull requests related to a commit. If you need to restore that behaviour, set this to "true". Defaults to "false".	no	false

Outputs

name	description
json	Test results as JSON