You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »


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.



Common Issues & Potential Solutions:


  • Software Version

Confirm whether you are using Xray Cloud or Xray Data Center and adapt to our documentation accordingly.


Readme

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


Importing using API

  • 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.
  •  

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.



Note:

Other Common Issues: 

Error Messages: Understand common error messages and their solutions.

For example, a 404 error might indicate that you’re trying to import results to the wrong server.

A “No Project” error might indicate an issue with the project key in your import file.

Software Version Issues: If you’re encountering issues after an Xray or Jira update, it could be a software bug. Check the Xray support portal for known issues and updates.


Looking to learn more:

Check out this: TTT: Examples using JUnit


  • No labels