Migrating Test Steps in Jama-to-Jama ReqIF Exchange Using DX

Overview

This article explains the challenges of migrating test steps when performing a Jama-to-Jama ReqIF Exchange using DX, including solutions and workarounds.

1. Issue: Test Steps Are Not Migrating in DX 3.9.3

✔ Problem Description:

• Test steps are included in the export mapping.

• However, on import, there is no "Steps" field available in ReqIF to map them.

• As a result, test steps do not appear in the imported test cases.

✔ Affected Versions:

• DX 3.9.3 does not properly carry over test steps in ReqIF migrations.

2. Workarounds for Migrating Test Steps in DX

A. Use the DX 3.9.4 Snapshot Version

✔ A snapshot version (DX 3.9.4) was created as a workaround to enable test step migration.
✔ Note: This version is untested by the development team and not officially supported.
✔ Download Link (Internal Use Only):

bash

CopyEdit

https://jamasoftware.slack.com/files/UB4N4AN4V/F075BV1UQ64/dataexchange-3.9.4-snapshot.jar

✔ Steps to Use the Snapshot Version:

1. Replace your current DX 3.9.3 JAR file with the DX 3.9.4 snapshot JAR.

2. Run the export/import process again and verify test step migration.

B. Enable the "Include Test Steps" Setting in DX

✔ Some users reported success by ensuring the "Include Test Steps" checkbox is enabled in DX.
✔ Steps to Verify:

1. Go to DX settings before export.

2. Check the option for "Include Test Steps".

3. Proceed with the export/import and confirm test step migration.

3. Best Practices for Ensuring Successful Test Step Migration

✅ Verify that test steps are included in the ReqIF file before import.
✅ Use DX 3.9.4 snapshot only if necessary, and be aware of its unsupported status.
✅ Confirm that "Include Test Steps" is enabled in DX settings.
✅ If test steps do not migrate, manually verify ReqIF mappings before import.

4. Conclusion

• DX 3.9.3 does not properly migrate test steps.

• A DX 3.9.4 snapshot version exists as a workaround but is unsupported.

• Ensuring the "Include Test Steps" setting is enabled in DX may resolve the issue.