Points to Know
The following are two ways for migrating the projects:
Using Project Migration Utility: Qualitia provides a Utility tp migrate multiple projects in a single instance.
Using Qualitia Client: From Qualitia v7.3.0, if you select a non-migrated project, an error message is displayed in Qualitia that prompts you to migrate the selected project only. Upon clicking Migrate Now on this message, Qualitia guides you for migration of the selected project only.
In each screen of the migration process, you have an option to go to the previous screen or cancel the migration process at any time.
Any user having database and version control tool credentials can run the Project Migration Utility.
Recommendations for Project Migration
Latest versions of test cases and tasks must be available in the Project path
The Qualitia database is accessible
Migration process might take extended time based on the project size. Therefore, plan to initiate migration accordingly.
Perform the project migration on a machine with at least below configurations for better turn-around time.
RAM - 16 GB
Quad-Core Processor
Free Disk Space - 5GB
Also, the migration process completes faster if other programs are not running on the machine.
Launching the Project Migration Utility
To launch the Project Migration Utility:
Open the Qualitia Installable.
Under the QualitiaProjectMigrationUtility folder, unzip the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.
Execute the QualitiaProjectMigrationUtility.exe
Migrating Projects
Project Migration using Qualitia Client
If you are migrating a single project from a Qualitia client, there is no need to enter database or version control details. If some project artifacts do not match with version control, Qualitia directly opens the details of artifacts missing screen, as described in step 5.
Else, it directly displays the Project Health Checkup screen as described in step 6..
Step 1: Launch the Project Migration Utility, the first screen opens as shown in the following figure:
Click Next.
Step 2: Enter the following database details.
Field | Description |
|---|---|
Database Type | Select the Server from the drop-down list: SQL Server and MySQL. |
Server Port | Enter the Server and the Port IDs. |
Authentication | Select the authentication type: Windows Authentication or SQL Server Authentication |
User Name | Enter the database server username |
Password | Enter the database server password. |
Database Name | Enter the database name which contains metadata of all the projects. |
Qualitia Server URL | Enter the URL where Qualitia Server is installed. The Qualitia Server URL is a combination of the hostname/IP and port 8887 where you have installed Qualitia server. |
Click Next.
Step 3: Select projects to migrate from the Projects Selection screen.
Click Next.
Step 4: Enter the Version Control details for the selected project.
Field | Description |
|---|---|
Version Control | Select the version control tool you are using for managing Qualitia project artifacts (Tasks and Test cases).* |
SVN Client | Select the SVN client version from the drop-down list. This option is available for SVN only. |
User Name | Enter the SVN/Bitbucket/GIT username. |
Password | Enter the SVN/Bitbucket/GIT password. |
In the case of multiple projects, the version control details are entered for every project one-by-one.
Click Next.
Step 5: If some test cases or tasks are missing for some projects, then the following are three types of validation errors highlighted for those projects:
Tasks with missing XML files: Shows the total number of tasks and name of each task that is missing.
Test Cases with missing XML files: Shows the total number of test cases and name of each test case that is missing.
Test Cases Impacted due to deletion of tasks: Shows number and name of test cases which are affected due to missing tasks.
In case you are able to find the missing test case/task XML files, add them in their respective project folders. Click Refresh to get the revised status of the missing files.
If files are not found, click Next to delete them.
The impacted tasks and test cases listed will not be available in the migrated project.
Step 6: The Project Migration Utility takes backup of the validated project artifacts, as shown in the following figure:
Click Next.
Step 7: The Project Health Check screen starts for each selected project as shown in the following figure:
Verification for a project can fail due to the following reasons:
The number of Test cases in the Project Database and Project path are not equal.
Some test cases of a project are locked by users.
The DB connection was interrupted.
Step 8: If verification fails for a project, click Corrective Actions to delete any test case or task file.
The Utility shows the problem in the test case or task XML file due to which verification failed.
Select the test case or task, and click Delete.
From the Project Health Check screen, click Retry to start the verification of that project.
Step 8: Click the Download Report to download the Project Health Check report. The report shows the status of verification for each test case and task along with their IDs and statuses. Also, the reason for a test case or task verification failure.
In the case of multiple projects:
You can migrate only those projects which were successfully verified.
If no project is verified successfully, a message is displayed, which shows that the migration process cannot proceed.
Click Next to start the Project Migration process.
Step 9: The Project Migration process starts as shown in the following figure:
Click Next.
Step 10: When a project migration is successful, the number of test cases and tasks are displayed along with their names, as shown in the following figure:
If all test cases and tasks are migrated successfully, it shows as “All tasks are Migrated Successfully” and “ All test cases are migrated successfully”.
Step 11: Click Finish to exit the Migration Utility.
Post Migration Considerations
After migrating a project, you must perform the following operations:
Recreate all the offline packages created using old Qualitia versions
If the project is integrated with TFS/Azure DevOps, then re-publish the test cases associated with TFS/Azure DevOps test cases.
Add Comment