Xray TypeScript & JavaScript client library for assisting on test automation tasks

xray-automation is a TypeScript & JavaScript library to assist on common test automation tasks, such as the ability to upload test results to Xray and Jira from your pipeline during CI/CD.

Core features:

supports Xray datacenter(DC)/server, and Xray cloud
upload test automation results in different formats
Promise based (e.g, .then().catch() ...)
upload results with standard parameters to identify Jira project, its version, revision, test environment..
upload results with ability to fully customize Test Execution and Test issues, using a more low-level request (that uses the "multipart" endpoint variant)

Background

This library provides an abstraction layer for the underlying APIs that Xray provides on the different Jira deployment flavours. Xray provides different kinds of APIs and also different endpoints to support importing of test results in different format. Xray's REST API is the main API used for this purpose. It's available both on Xray datacenter/server and also on Xray cloud; there some slight differences between them. The REST API provides the ability to import results (both on Xray DC/server and Xray cloud), and also the ability to manage the relation between entities (Xray DC/server only). The GraphQL API is only available on Xray cloud; it provides the ability to manage relation between entities on Xray cloud.

Installation

npm i @xray-app/xray-automation

Usage

This library provides two main objects, XrayDatacenterClient and XrayCloudClient, that provide the ability to interact with Xray on Jira datacenter/server or with Xray on Jira Cloud, respectively. Therefore, and first of all, you must know which Jira deployment variant you're using.

Client initialization and configuration

For Xray cloud we need to use a client id + client secret pair, from a API key defined in Xray. Please see API keys (client id + client secret pair) on Xray cloud.

For TypeScript:

import { XrayCloudClient, XraySettings } from '@xray-app/xray-automation'

const xrayCloudSettings: XraySettings = {
    clientId: '0000000000',
    clientSecret: '1111111111',
    timeout: '30000'
}; 

const xrayClient: XrayCloudClient = new XrayCloudClient(xrayCloudSettings);

For JavaScript:

import { XrayCloudClient } from '@xray-app/xray-automation'

const xrayCloudSettings = {
    clientId: '0000000000',
    clientSecret: '1111111111',
    timeout: '30000'
}; 

const xrayClient = new XrayCloudClient(xrayCloudSettings);

For Xray server/datacenter, we can use basic authentication and provide a Jira username/password. For Xray datacenter on a compatible Jira DC version (>= 8.14), we can also use PAN (Personal Access Tokens).

For TypeScript:

import { XrayDatacenterClient, XraySettings } from '@xray-app/xray-automation'

const configWithCredentials: XraySettings = {
    jiraBaseUrl: 'http://myserver.jira.local',
    jiraUsername: 'username',
    jiraPassword: 'password',
    timeout: '30000'
};

// or...

const configUsingToken: XraySettings = {
    jiraBaseUrl: 'http://myserver.jira.local',
    jiraToken: 'xxxxxx',
    timeout: '30000'
};

const xrayClient: XrayDatacenterClient = new XrayDatacenterClient(configWithXXX);

For JavaScript:

import { XrayDatacenterClient } from '@xray-app/xray-automation'

const configWithCredentials = {
    jiraBaseUrl: 'http://myserver.jira.local',
    jiraUsername: 'username',
    jiraPassword: 'password',
    timeout: '30000'
};

// or...

const configUsingToken = {
    jiraBaseUrl: 'http://myserver.jira.local',
    jiraToken: 'xxxxxx',
    timeout: '30000'
};

const xrayClient = new XrayDatacenterClient(configWithXXX);

Optionaly, we may also set a timeout (in ms) that will be used whenever making requests to Xray. The default is 50000 (i.e., 50 seconds).

Import test results to Xray (basic scenario)

To import results, we need to use the method submitResults(reportFile, reportConfig) on the respective Xray client object.

reportFile: file with the test results (relative or absolute path)
reportConfig: an object with additional settings, mostly to assign values on the corresponding Test Execution issue; possible values on the table ahead.

setting	description	mandatory/optional	example
`format`	format of the report (import&use JUNIT_FORMAT, TESTNG_FORMAT, NUNIT_FORMAT, XUNIT_FORMAT, ROBOT_FORMAT, CUCUMBER_FORMAT, BEHAVE_FORMAT, XRAY_FORMAT)	mandatory	XRAY_FORMAT (or "xray")
`projectKey`	key of Jira project where to import the results	mandatory (doesn't apply to "cucumber" or "behave" report formats, for legacy reasons)	CALC
`testExecKey`	issue key of Test Execution, in case we want to update the results on it	optional	CALC-2
`testPlanKey`	issue key of Test Plan to link the results to	optional	CALC-1
`version`	ersion of the SUT, that corresponds to the Jira project version/release; it will be assigned to the Test Execution issue using the "fixVersion(s)" field	optional	1.0
`revision`	`xray.revision`	source code revision or a build identifier	optional
`testEnvironments`	usually, a test environment name/identifier (e.g., browser vendor, OS version , mobile device, testing stage)	optional	[chrome]

For TypeScript:

import { XrayDatacenterClient, XrayCloudClient, ReportConfig, JUNIT_FORMAT } from '@xray-app/xray-automation'

let reportFile = 'report.xml';
let reportConfig: ReportConfig = {
    format: JUNIT_FORMAT,
    projectKey: 'BOOK',
    version: '1.0',
    revision: '123',
    testPlanKey: 'CALC-10',
    testExecKey: 'CALC-11',
    testEnvironments: [],
}

let res = await xrayClient.submitResults(reportFile, reportConfig);
console.log('Test Execution key: ' + res.key);

For JavaScript:

import { XrayDatacenterClient, XrayCloudClient, JUNIT_FORMAT } from '@xray-app/xray-automation'

let reportFile = 'report.xml';
let reportConfig = {
    format: JUNIT_FORMAT,
    projectKey: 'BOOK',
    version: '1.0',
    revision: '123',
    testPlanKey: 'CALC-10',
    testExecKey: 'CALC-11',
    testEnvironments: []
}

let res = await xrayClient.submitResults(reportFile, reportConfig);
console.log('Test Execution key: ' + res.key);

Please note that Xray server/DC and Xray cloud support mostly the same formats, but not exactly for legacy reasons. Besides, not all formats support the same parameters; please check the respective product documentation. The following table sums this info.

report format	supported Xray variant	notes
xray	cloud and server/DC	the format is not exactly the same as Xray and Jira itself are different on server/DC and cloud
junit	cloud and server/DC
xunit	cloud and server/DC
nunit	cloud and server/DC
robot	cloud and server/DC
testng	cloud and server/DC
cucumber	cloud and server/DC	in this specific case, it's not possible to use the parameters `projectKey`, `version`, `revision`, `testPlanKey`, `testExecKey`, `testEnvironments` (due to the way the underlying "standard" endpoint for Cucumber works)
behave	cloud and server/DC	in this specific case, it's not possible to use the parameters `projectKey`, `version`, `revision`, `testPlanKey`, `testExecKey`, `testEnvironments` (due to the way the underlying "standard" endpoint for Cucumber works)

Import test results to Xray with customization of Test Execution and Test issues (advanced scenario)

Related to each report format (e.g., "junit") , there's a "standard" endpoint (e.g., ".../import/junit") and a "multipart" endpoint one (e.g., ".../import/junit/multipart")

The "standard" Xray REST API endpoints allow us to pass some well-known parameters to identify the target project and its version, for example. However, sometimes we may need to customize additional fields on the Test Execution issue that will be created whenever uploading test results. For that, we have to use the "multipart" endpoint which has a completely different syntax.

To import results with customization possibilities, which internally will use the proper "multipart" endpoint for that test report format, we need to use the method submitResultsMultipart(reportFile, reportConfig) on the respective Xray client object.

reportFile: file with the test results (relative or absolute path)
reportConfig: an object with additional settings; possible values on the table ahead.

setting	description	mandatory/optional	example
`format`	format of the report (import&use JUNIT_FORMAT, TESTNG_FORMAT, NUNIT_FORMAT, XUNIT_FORMAT, ROBOT_FORMAT, CUCUMBER_FORMAT, BEHAVE_FORMAT, XRAY_FORMAT)	mandatory	XRAY_FORMAT (or "xray")
`testExecInfoFile`	path to a JSON file containing attributes to apply on the Test Execution issue that will be created, following Jira issue update syntax	mandatory (if testExecInfo is not provided)	-
`testExecInfo`	JSON object containing attributes to apply on the Test Execution issue that will be created, following Jira issue update syntax	mandatory (if testExecInfoFile is not provided)	-
`testInfoFile`	path to a JSON file containing attributes to apply on the Test issues that may be created, following Jira issue update syntax	optional	-
`testInfo`	JSON object containing attributes to apply on the Test issues that may be created, following Jira issue update syntax	optional	-

For TypeScript:

import { XrayDatacenterClient, XrayCloudClient, ReportConfig, JUNIT_FORMAT } from '@xray-app/xray-automation'

...
let testExecInfoJson = { 
    "fields": {
        "project": {
            "key": "CALC"
        },
        "summary": "Test Execution for Junit tets",
        "description": "This contains test automation results"
    }
};

let multipartConfig: ReportConfig = {
    format: JUNIT_FORMAT,
    testInfoFile: 'testInfo.json',
    // testInfo: testInfoJson,
    testExecInfoFile: 'testExecInfo.json',
    // testExecInfo: testExecInfoJson,
}

let res = await xrayClient.submitResultsMultipart(file: reportFile, config: multipartConfig);
console.log('Test Execution key: ' + res.key);

For JavaScript:

import { XrayDatacenterClient, XrayCloudClient, JUNIT_FORMAT } from '@xray-app/xray-automation'

...
let testExecInfoJson = { 
    "fields": {
        "project": {
            "key": "CALC"
        },
        "summary": "Test Execution for Junit tets",
        "description": "This contains test automation results"
    }
};

let multipartConfig = {
    format: JUNIT_FORMAT,
    testInfoFile: 'testInfo.json',
    // testInfo: testInfoJson,
    testExecInfoFile: 'testExecInfo.json',
    // testExecInfo: testExecInfoJson,
}

let res = await xrayClient.submitResultsMultipart(file: reportFile, config: multipartConfig);
console.log('Test Execution key: ' + res.key);

Associate Test Execution to Test Plan

Whenever using the submitResults method, and for most formats, it´s possible to associate the Test Execution to an existing Test Plan. However, for some formats (and respective endpoints), this may not be possible. Also, on multipart endpoints it may not be something straightforward (e.g., you may need to know the Test Plan custom field id for Jira server/DC).

For TypeScript:

let testExecKey = 'CALC-11';
let testPlanKey = 'CALC-10';
let res = await xrayClient.associateTestExecutionToTestPlan(testExecKey, testPlanKey);

// or if you know the issue ids... (Xray on Jira cloud only)
// let res = await xrayClient.associateTestExecutionToTestPlanByIds('10001', '10000');

console.log('Test Execution key: ' + res.key);

For JavaScript:

let testExecKey = 'CALC-11';
let testPlanKey = 'CALC-10';
let res = await xrayClient.associateTestExecutionToTestPlan(testExecKey, testPlanKey);

// or if you know the issue ids... (Xray on Jira cloud only)
// let res = await xrayClient.associateTestExecutionToTestPlanByIds('10001', '10000');

console.log('Test Execution key: ' + res.key);

Other tips

Implementing a retry strategy

To implement retries, for example if the server is giving some error such as telling you that you've surpassed the allowed thorughput limit (HTTP status code 429), you can use the promise-retry package and implement something like the following snippet of code.

    promiseRetry(function (retry, number) {
        console.log('attempt number', number);

        return xrayClient.submitResults(reportFile, reportConfig)
        .catch(function (error) {
            if (error.response.status === 429) {
                retry(error);
            }
            throw error;
        });
    }, { retries: 2 })
    .then(function (response) {
        console.log('test_exec: '+ response.key);
    }, function (error) {
        console.log('response: '+ error._response);
        console.log('HTTP STATUS CODE: '+ error.statusCode);
    });

FAQ

If we have questions/support issues, where should those be addressed?

It's an open-source project, so it should be handled in this GitHub project and supported by the community. If you want to use the previous, proprietary plugin, you can do so and that has commercial support, if you have a valid license.

Are the underlying APIs the same for Xray server/datacenter and Xray Cloud? Are the available options the same? Are the supported test automation report formats the same?

Not exactly. Xray server/datacenter and Xray cloud, even though similar, are actually distinct products; besides Jira server/datacenter and Jira cloud are different between themselves and have different capabilities. This plugin makes use of the available REST APIs for Xray server/datacenter and Xray cloud, so you should check them to see exactly what is supported for your environment.

Do I need to use this library to upload test results to Xray? Can't we use something more tailored to our own CI/CD tool?

Xray provides several free plugins for Jenkins, Bamboo, and TeamCity. You can use them out-of-the-box. In Xray documentation, you may find more info about these and other instructions on how to upload test results from other CI/CD tools.

So, if you have specific plugins/instructions for the most diverse CI/CD tools... why do you need this library?

Sometimes teams may want to manage the logic for uploading test results (e.g., after finishing some task/event). This library can be useful in those scenarios, if you're using JavaScript and NodeJS.

Contact

You may find me on Twitter. Any questions related with this code, please raise issues in this GitHub project. Feel free to contribute and submit PR's. For Xray specific questions, please contact Xray's support team.

Disclaimer

This project is in early stage; the setting names and other are subject to change.

Acknowledgments

C-J Kihl

TO DOs

implement cucumber related operations/endpoints
timeout configuration for GraphQL requests
review/refactor tests
REST API v1 support?
review error handling
review modules support

Changelog

References

LICENSE

BSD 3-Clause

Name		Name	Last commit message	Last commit date
Latest commit History 73 Commits
.github/workflows		.github/workflows
.husky		.husky
__tests__		__tests__
config		config
coverage		coverage
src		src
tools		tools
types		types
.eslintrc.cjs		.eslintrc.cjs
.gitignore		.gitignore
.npmignore		.npmignore
CHANGELOG.md		CHANGELOG.md
LICENSE		LICENSE
README.md		README.md
RELEASING.md		RELEASING.md
SECURITY.md		SECURITY.md
jest.config.js		jest.config.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json
tslint.json		tslint.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Xray TypeScript & JavaScript client library for assisting on test automation tasks

Background

Installation

Usage

Client initialization and configuration

Import test results to Xray (basic scenario)

Import test results to Xray with customization of Test Execution and Test issues (advanced scenario)

Associate Test Execution to Test Plan

Other tips

Implementing a retry strategy

FAQ

Contact

Disclaimer

Acknowledgments

TO DOs

Changelog

References

LICENSE

About

Releases 3

Languages

License

Xray-App/xray-automation-js

Folders and files

Latest commit

History

Repository files navigation

Xray TypeScript & JavaScript client library for assisting on test automation tasks

Background

Installation

Usage

Client initialization and configuration

Import test results to Xray (basic scenario)

Import test results to Xray with customization of Test Execution and Test issues (advanced scenario)

Associate Test Execution to Test Plan

Other tips

Implementing a retry strategy

FAQ

Contact

Disclaimer

Acknowledgments

TO DOs

Changelog

References

LICENSE

About

Topics

Resources

License

Security policy

Stars

Watchers

Forks

Releases 3

Languages