Xray GraphQL API

GraphQL gives clients the power to ask for exactly what they need and nothing more.

Xray now provides a GraphQL API that allows users to perform CRUD operations directly on Xray entities. The GraphQL API works in conjunction with the existing REST API.

Learn more here.

Tests by Test Type

This gadget allows users to group Tests by Test Type (e.g. Manual, Cucumber, Generic...). The source can either be a project or a saved filter.

Learn more here.

Overall Test Results

This gadget allows users to group Tests by Test Status. Users can immediately see the testing status of a project or set of issues, just by looking at this gadget.

On the gadget configuration, users can set the analysis scope and source. The source can be either a project or a saved filter. With the analysis scope, users can calculate the Test Status by:

• Latest: considering the latest execution for each Test,
• Version: considering only Test Executions for a specific version
• Test Plan: considering only Test Executions with the context of a Test Plan.

Learn more here.

Export Xray reports as CSV files

Almost all Xray reports can now be exported as CSV files, including:

• Traceability Report
• Tests List
• Test Sets List
• Test Executions List
• Test Plans List
• Test Runs List

New REST API endpoint for importing Cucumber feature files allowing new usage scenarios, including using Git as master

A new idempotent REST API endpoint will make it possible to import Cucumber Background, Scenario and Scenario Outlines from existing Cucumber .feature files.

This endpoint will leverage new usage scenarios for Cucumber.

Now you can either use Xray and Jira as the master for edition of Cucumber based Tests/Preconditions or you can use Git instead, for example, and keep using your favorite IDE for editing them.

In this new supported workflow, Cucumber features will be "managed" in the source code VCS (versioning control system). This means that users will be editing features elsewhere, other than Jira, and will synchronize the scenarios contained within those features back to Jira. Therefore the master of information will be Git, SVN or whatever VCS is being used; you just need to make sure you follow some rules for tagging the Scenarios so they can be properly mapped to Xray.

You can also migrate your existing Cucumber projects into Jira and start managing them in Xray instead.

Learn more about the new endpoint here and about the new supported Cucumber workflow and usage scenarios here.

As of now, Xray supports multipart requests when importing execution results. This allows additional information to be sent for the Test Execution issue that will be created/updated. The additional information part is a JSON document with the same format used in Jira to update issues.

Learn more here.

Support for xUnit test results

xUnit.net is a technology for unit and integration testing C#, F#, VB.NET and other .NET languages. xUnit.net works with ReSharper, CodeRush, TestDriven.NET and Xamarin. It is part of the .NET Foundation.

Xray now supports xUnit execution results. You can send directly the XML report generated by xUnit into Xray, either using the REST API or the user interface.

Learn more here.