FAQs - Zephyr Migration from qTest

When can I start Migrating

We recommend migrating data anytime after the upgrade to Zephyr Essential (date TBD). Once Zephyr Essential is available to all users in Prod, the ability to create new projects will be removed in qTest.

We recommend reviewing the runtime of projects currently in flight. If a project is expected to be completed before November, it may be better to finish it in qTest rather than migrate to ensure all test executions are captured in the existing project for exporting as a whole should they be needed for audit. However, for projects that will run past November, we suggest prioritizing their migration as soon as possible to begin building that test case and execution repository within the new tool.

Additionally, on December 1st, access to qTest will be turned off to ensure a proper archive backup can be created.

What can we export?

qTest allows users to export data for reporting and analysis in various formats, including Excel and HTML. Key export features include requirements, test cases, traceability matrices, and test execution results. Additionally, when these are exported, all attachments will be included.  These attachments have a link generated in the excel file to them on the corresponding test case row.

Recommendation:

• qTest Test Cases are reviewed and cleaned up prior to export to reduce file size

  • If attempting to export all Test Cases at the parent/top level and it exceeds file size limitation, consider creating a folder structure in qTest to organize groups of test cases in a logical fashion and then exporting each as its own set to upload separately.

• qTest Test Executions are reviewed and cleaned up prior to export to reduce file size

  • If attempting to export all Test Executions at the parent/top level and it exceeds file size limitation, consider creating a folder structure in qTest to organize groups of test cases in a logical fashion and then exporting each as its own set to upload separately.

  • It is recommended that the Test Cases are imported into Zephyr Essential. If following this process, consider if a copy of the Test Executions is even needed for personal records as the Atlassian Administration team will be exporting all Test Executions deemed necessary for the Audit copy prior to qTest deactivation.

How do we export?

• A comprehensive set of instructions will be provided to team leads with details on how to do this. Once created it can be found here.

Where do we export?

• Data that will be imported to Zephyr: Exports can be downloaded and reused for system uploads.

• Data that will be Archived: If there are cases or datasets you’d like to hold onto for potential future needs or reference, these can be stored in a location of your choosing.  We suggest somewhere that is backed up.  Also ensure that you keep the original zip file that is generated in the event you choose to move the save somewhere else.  The links to attachments will not work if the folder is moved post decompression.

• Data for Audits: A master dataset will be exported to a restricted-access share to ensure integrity and preserve an untouched copy for audits.

What can we import?

Zephyr Essentials can import CSV files from qTest. A step-by-step guide is provided below to help users map fields correctly and complete the import process. While all fields and data can be transferred, attachments from qTest exports cannot be imported. if you want to preserve attachment links, we recommend running a VB script in Excel to add the attachment link to the description field before saving your export as a csv file.

Recommendation:

While a Test Execution export from qTest can be imported into the Test Case section of Zephyr Essential, it is not recommended. The mapping will be more complex and only the Test Cases and steps will be captured.

How do we import?

• A comprehensive set of instructions is provided below with details on how to do this. 

Where can I find training on Zephyr Essential?

• Zephyr Essentials offers several resources to help users familiarize themselves with its functionality and interface. SmartBear, the vendor, provides a guide in their support section. While guidance on features and functionality will be available, test leads will be responsible for defining the process.

Who will be migrating the data?

• The testing teams will be responsible for performing the data migration, as they best understand what needs to be transferred and how it should be structured. The Atlassian team will provide tools to facilitate an efficient migration process and will be available to offer guidance and support as needed.

Who will perform the archive for the Audit?

• The Atlassian admin team will collaborate with the test leads, FDM’s and Auditing team to perform this task.  It will require finding the secure location and working with teams to ensure everything needed is captured.

Is there an other documentation?