mikepenz/xray-action

GitHub action to import test results into "Xray" - A complete Test Management tool for Jira.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 8, 2026
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: mikepenz/xray-action@2b268086cd2fc5a78bbada2d791286c96077f44b # v4.1.1

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

namedescriptionrequireddefault
xrayCloudDefines which variant of Xray to target at [cloud vs Server/DC]notrue
xrayBaseUrlDefines the base URL for Xray Server/DC, could be used to change XRay Data region for XRay Cloud (required if xrayCloud="false")no
usernameXray API client id (cloud) or Jira username (Server/DC). (Required for xrayCoud)no
passwordXray API client secret (cloud) or Jira password (Server/DC). (Required for xrayCoud)no
xrayTokenXray Personal Access Token. If provided username/password are ignored. (Xray Server/DC only)no
testPathsA `glob` pattern, to find all test results which should get imported.yes**/test-results/test/TEST-*.xml
testMergeWhen multiple test reports are found, they will be automatically merged into a single test report file. Only supported for: ["junit"]notrue
testFormatThe format of the to be imported data. ["xray", "cucumber", "behave", "junit", "testng", "nunit", "xunit", "robot", "bundle"].junit
testExecKeyKey of the Test Execution.yes
projectKeyKey of the project where the Test Execution (if the testExecKey parameter was not provided) and the tests (if they are not created yet) are going to be created.yes
testPlanKeyKey of the Test Plan; if you specify the Test Plan, the Tests will be added automatically to the Test Plan if they are not part of it.no
testEnvironmentsA string containing a list of test environments separated by ";". This is not supported for cloud.no
revisionSource code and documentation version used in the test execution.no
fixVersionThe Fix Version associated with the test execution (it supports only one value).no
combineInSingleTestExecIf no `testExecKey` is provided, it will generate a testExec with the first import, and reuse the same for all other imports.nofalse
failOnImportErrorDefines if the action should fail if an import error occurred.nofalse
continueOnImportErrorDefines if the action should continue after a single import error occurred.notrue
importParallelismSpecifies the level of parallelism to import to Xray.no2
responseTimeoutSpecifies the maximum duration for a request (in milliseconds) to wait for a response to execute before timing out. The default is 60 seconds.no60000
importRetryLimitSpecifies the maximum number of retries for failed import requests. The default is 2.no2
testExecutionJsonLinks to a json file, defining the meta information to create the test execution ticket.no
testJsonLinks to a json file, defining the meta information to create the test tickets.no
namedescription
countThe count of imported files.
failedThe count of failed imports.
completedThe count of completed imports.
errorMessageThe message of failed imports.
errorStatusCodeThe status code of failed imports.