Recommendations for Project Migration
You must have access to QFD database and version control, and to QAS 8.0.0 database.
The project path must be updated with latest versions of test cases and tasks.
The migration process might take an 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, extract the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.
Execute the QualitiaProjectMigrationUtility.exe
Migrating Projects
Step 1: Launch the Project Migration Utility,.
From the first screen, click Next.
Step 2:
Enter the details to connect to a database.
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. |
Step 3: Under Project Selection, do the following:
Select the QFD projects you want to migrate.
Click Next.
Step 5: The Utility validates whether all the tasks and test cases in the project path are present.
For every project it shows the results for the following three types of validation:
Tasks with missing XML files: Shows the tasks that are missing
Test Cases with missing XML files: Shows the test cases that are missing.
Test Cases Impacted due to the deletion of tasks: Shows the test cases that are associated with the missing tasks.
Perform the following steps:Do one of the following:
To add the missing test case/task XML files: Find and add them in their respective project folders., and click the Refresh button.
The Utility screen updates the missing tasks and test cases.To skip the missing test case and task files, click Next.
If you skip the missing files, the migrated projects will not have the missing test cases and tasks.
Step 6: The Project Health Check starts for each selected project.
Verification for a project may 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 the project are locked.
If the connection to DB is interrupted.
Step 7: The Verification of Project Artifacts shows verifications failed in test cases and tasks XML file for every project.
If verification fails for a project, perform the following steps:
Click Download Report to view the test cases, tasks, and custom action VB files.
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.Click Corrective Actions to delete test cases or task files having technical problems.
Click Custom Actions to add dummy VB files for the missing VB files.
Click Retry after updating the project artifacts to re-verify the project artifacts.
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 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.
Step 9: Qualitia 8.0 Database details screen opens.
Enter the following database details for the Qualitia Automation Studio to which you want to migrate.
Type: Lets you select the database type, MySQL or SQL Server.
Server: Port: Lets you specify the database server address along with its Port Id. The default Port Id for MySQL is 3306 and for SQL Server is 1433.
Database Name: Lets you specify the Master Database name.
Authentication: Lets you authenticate the SQL Server using Windows credentials.
User Name: Lets you specify the username to connect with the database.
Password: Lets you specify the password for authentication.
Project Path: Specify the folder where Qualitia project artifacts (test cases and tasks) are saved.
Take Database backup: Enables to take the backup of QFD projects.
Step 10: If you have taken the backup, then project backup starts.
After project backup completes, click Next.
Step 11: The project migration starts. After project migration completes, click Next.
Step 10: The Project Migration Summary opens.
For every project, if all test cases and tasks are migrated successfully, it shows as “All tasks are Migrated Successfully” and “ All test cases are migrated successfully”.
Click Finish to exit the project migration utility.
Post Migration Considerations
You need to recreate offline suites using the offline package. For more information, refer to Offline Package