Test Imports
Test imports give you the option of detecting conflicts between modified source code and the source code of a software component (SC) that is pending import. You can use them in both Development and Consolidation systems.
You can see the results of the test import under Import Check State in the import queue.
The following are possible statuses:
● Import-check finished without Conflicts: The test import did not produce any conflicts and you can start the import.
● Import-check finished with Conflicts: The test import detected conflicts. To display the log of the test import, choose Details → Logs → Import Check → View Log File. Here, you can see which sources are affected. You can analyze the results and decide whether to run the import or not.
● Import-check running: The test import is running.
● Import-check failed: The test import failed with errors. Remove the cause of the error and start the test import again.
● Import-check not started: Test import is initial and can be started.

The test import can only detect conflicts between the inactive workspace and the SC that is waiting to be imported. The check does not detect any conflicts within the workspace.
You are in the Transport Studio of the Change Management Service (CMS).
You have selected the import queue of the development system or consolidation system.
You have SCs pending import in the import queue.
To perform a test import:
...
1. Select the SC for which you want to test the import.
2. Choose Import-Check. A confirmation dialog informs you that the results of the test import are temporary and can be invalidated by imports that are running in parallel.
3. Confirm the dialog. CMS performs the test import. The result of the test import appears in the Import Check State column.
You have completed a test import. Decide how to continue on the basis of the results. You can do the following:
● Import into the track.
● Import into a new track in order to perform a modification adjustment.