Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Introduction


This article provides a guide to troubleshooting common issues and optimizing your testing workflow when importing tests using the Xray API or UI on both Jira Data Center and Jira Cloud.

...

You may also have authentication errors as described below:

  • 400 Bad Request - Possibly linked to a wrong request syntax
  • 401 Unauthorized - Possibly linked to your Xray license may no longer be valid
  • 500 INTERNAL SERVER ERROR - An internal error occurred when authenticating the request.
  • Occasionally, your authentication token may be revoked and will give you an error. This is due to



Info
titleReadme

The method you choose to import your test results will determine the aspects you need to address.

...

  • API Version Issues:

    If you are encountering issues with the v1 API, consider switching to the v2 API.
  • Incorrect API Endpoint: 

    Make sure you’re using the correct API endpoint for importing test results. For Xray Cloud, the endpoint is different from the one used for Xray Data Center.
  • Data Format Issues:

    Ensure your test results are in the correct format. For example, when importing JUnit results, make sure your tests are generating JUnit reports in the correct format.
    • Verify JUnit Structure → Taking advantage of JUnit XML reports
    • When importing data via an API, format issues often arise in the request. For instance, when using the curl command, an incorrect number of quotation marks or hidden characters can cause the request to fail.

    • Parameter-related issues are also frequent. If you provide the wrong Project key or Test Key, it can lead to problems during the import process.

  •  

Importing using UI

  • Data Format Issues:

    Ensure your test results are in the correct format. For example, when importing JUnit results, make sure your tests are generating JUnit reports in the correct format.

...