Post-migration steps

After completing the migration, take the following steps:

1. Remove the old cache keys. Details...
2. Update the AD integration and authentication settings. Details...
3. Validate the Insights migration. Details...
4. Validate the Test Manager migration. Details...

Step 4: Validating the Test Manager migration

To ensure a successful synchronization between Test Manager and ALM systems, follow these steps to reconfigure the Test Manager in Automation Suite:

1. Reconfigure the Automation Suite Test Manager URL in your ALM systems to reflect the correct location of the Test Manager.
2. Confirm that you can access Test Manager using the updated Automation Suite URL.
3. Ensure all projects and their underlying resources, including test cases, requirements, and related data, are fully restored and accessible.
4. Confirm that all attachments are correctly located in the external storage and can be downloaded without issues.
5. Reconfigure robots to point to the correct Orchestrator URL to ensure they function properly.
6. Update the Test Manager URL in Studio with the updated Test Manager in Automation Suite URL.

Troubleshooting

1. If migration fails due to another operation that is already in progress, this occurs when ArgoCD is actively processing another job or deployment for Test Manager, preventing the migration script from executing. To solve this, follow these steps:
   1. Open the Arco CD UI and check the status of running processes related to Test Manager.
   2. Wait until all processes are completed, and confirm that all pods are in a healthy state.
   3. Re-run the the Test Manager migration script.
2. If the script fails to execute due to a bad interpreter, follow these steps:
   1. Open a terminal in the directory where the Test Manager migration script is located.
   2. Run the following command:

      dos2unix testmanager_migrator.sh