Points to Know
The following are two ways for migrating the projects:
Using Project Migration Utility: Qualitia provides a Utility to 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.The QFD Migration Utility lets you migrate your QFD projects to Qualitia Automation Studio 8.0.x.
| Info |
|---|
You can upgrade to QAS v8.0.x without uninstalling QFD. Also, QAS 8.0.x and QFD can be installed on the same computer. |
Rules and Recommendations for Project Migration
Qualitia recommends that you run the QFD Migration Utility on any of the Qualitia client machines. Ensure that the selected Qualitia client machine already have the prerequisites for running the utility and the project folders are integrated with version control systems (SVN).
QAS 8.0.x server must be installed before you start the QFD project migration.
QAS 8.0.x server must be configured with the same database management (MySQL or Microsoft SQL) as QFD server. For example, if the QFD server is configured with MySQL, then QAS server must also be configured using MySQL.
You must upgrade to QFD version 4.3.11 before migrating your QFD projects.
Ensure that you have access to:
QFD database
SVN (if it is integrated with QFD)
QAS 8.0.x database
Update the project path to the latest versions of test cases and tasks.
Plan the migration as the process may take more time for large projects.
For a better turn-around time for the migration process, Qualitia recommends using a computer with the following configuration:
16 GB RAM or more
Quad-Core Processor
5GB Free Disk Space or more
Close all the programs for better performance
Launching the Project Migration Utility
To launch the Project Migration Utility:
Open the Qualitia InstallableInstallation Package.
Under the QualitiaProjectMigrationUtility folder, extract .
Extract the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.
Execute the QualitiaProjectMigrationUtility.exe
Migrating Projects
| Info |
|---|
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,.
From the first screen, click Next.
...
Step 2:
Do the following in the order listed:
...
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.
The default port is 3306 for MySQL and 1433 for SQL.
...
Authentication
...
Select the authentication type: Windows Authentication or SQL Server Authentication
This field is applicable for SQL server only.
...
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.
For example, http://192.112.33.123:8887.
By default, Qualitia uses port 8887. You may change it while installing Qualitia Server component.
...
Step 3: Under Project Selection, select projects to migrate from the Projects Selection screen.
...
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.
| Info |
|---|
In the case of multiple projects, the version control details are entered for every project one-by-one. |
...
Performing the Project Migration Process
The Utility performs the project migration in the following three phases:
Finding the missing project artifacts for the selected projects
Conducting Health Check on the selected projects
Starting the Project Migration for the selected projects
To migrate the projects:
Step 1: Open the Qualitia Project Migration Utility.
On the Welcome to Qualitia Project Migration screen, review the recommendations, and click Next.
...
Step 2: On the Qualitia for Desktop (QFD) Database/Version Control Information screen, enter the following details, and click Next.
Type: Select the database type of QFD database, MySQL or SQL Server.
Server: Port: Specify the QFD database server address along with its Port Id. The default Port Id for MySQL is 3306 and for SQL Server is 1433.
Database Name: Specify the Master Database name of the QFD database.
Authentication: If you have selectedSQL Server database, select this option to authenticate to the SQL Server using Windows credentials.
User Name: Specify the username to connect to the QFD database.
Password: Specify the password for authentication.
Version Tool: Select SVN or None. If you select SVN, enter your SVN username and password to connect to SVN server.
Project Path: Specify the location of the folder where QFD saves the project artifacts (test cases and tasks).
Backup database before migration: Select this option to back up the selected QFD projects before starting the migration. You can skip this option if you have already backed up the selected project.
...
Step 3: On the QFD Project Selection screen, do the following:
Select the QFD projects that you want to migrate.
Click Next.
Step 4: On the Missing Artifacts Validation screen, review the information, and click Next.
For every project it shows the results for the following three types of validation:
Tasks with missing XML files: Shows Displays the total number of tasks and name of each task that is missingmissing tasks.
Test Cases with missing XML files: Shows the total number of test cases and name of each test case that is missing Displays the missing tasks.
Test Cases Impacted due to the deletion of tasks: Shows number and name of Displays the test cases which are affected due to that are associated with the missing tasks.
...
Remarks: Displays if all the necessary artifacts are available. Click Next if all the artifacts are available.
Perform the following steps if any of the artifacts are missing:Find and add the missing test case/task XML files
...
in their
...
associated project folders
...
If files are not found, click Next to delete them.
| Info |
|---|
The impacted tasks and test cases listed will not be available in the migrated project. |
Step 6: The Project Health Check screen starts for each selected project as shown in the following figure:
...
, and click the Refresh button.The Utility screen updates the missing tasks and test cases.
Click Next.
| Info |
|---|
You can skip the missing artifacts for a project if you are cannot find some missing tasks and test cases. After the project is migrated, you need to re-create the missing tasks and test cases. |
...
Step 5: On the Conducting Project Health Check screen, the project health check starts for the selected projects. The QFD Migration Utility verifies whether all the project artifacts for each project are correct and then generates a Health Check report as an HTML file.
| Info |
|---|
The project health checkup may fail if:
|
...
|
...
|
...
|
...
|
...
|
Step 7: 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.
...
| Info |
|---|
In the case of multiple projects:
|
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 Click Next, if the health check verification is successful for all the projects.
Perform the following steps, if the verification fails for any project due to incorrect or missing project artifacts.
Click Download Report to download the Migration Health Check report.
In the Migration Health Check report, click Test Cases and Tasks sections to know the test cases and tasks that are incorrect.
To resolve the validation issues, fix the incorrect test cases and tasks manually.
In the QFD Migration utility, click Corrective Actions to delete incorrect test cases and tasks if you could not resolve them.
Note: Unless the incorrect test case or tasks are resolved or deleted, you cannot migrate the project.
In the Migration Health Check report, click the Custom Action section to view the missing and duplicate custom actions.
Do the following in the order listed:Remove the duplicate custom actions.
For the missing custom actions, find and add them to the Project Path.
On the QFD Migration Utility, click Custom Actions to work around the missing actions if you are unable to resolve them.
Click Create Script to create dummy custom actions with empty methods for each missing custom action.
After updating the project artifacts, click Retry to perform the health check on the projects again.
Do one of the following:
If the health check verification fails for a project, then download the Health Check report to resolve the issues as explained in the steps above.
If the health check verification is successful for all the projects, click Next to start the project migration.
| Info |
|---|
If you click Next, you go ahead only with those projects that were successfully verified. |
...
Step 6: Onthe Qualitia 8.0 Database Details screen, enter the following details,and click Next.
Type: Select the database type for QAS v8.0.x, MySQL or SQL Server.
Server: Port: Specify the QAS v8.0.x database server address along with its Port Id. The default Port Id for MySQL is 3306 and for SQL Server is 1433.
Database Name: Specify the Master Database name of QAS v8.0.x.
Authentication: If you have selected SQL Server database, select this option to authenticate to the SQL Server using Windows credentials.
User Name: Specify the username to connect with the QAS v8.0.x database.
Password: Specify the password for authentication.
Project Path: Specify the folder where Qualtia v8.0.x saves the project artifacts (test cases, tasks, and custom actions).
Step 7: On the Generating Database Scripts for Migration screen, the progress of generation of database scripts that are required for migration is displayed. If you have opted to back up the database in step 2, then a backup of the selected projects is created in the QFD database.
After the project backup completes, click Next.
The following confirmation message appears:
The process cannot be reverted and should not be interrupted, interrupting the process leaves the project in the unusable state.
Click Yes to start the project migration, or click No if you want to migrate the project later.
...
Step 8: On the Updating Database to Qualitia 8.0 screen, the progress of updating the new XML schema to the Qualitia Automation Studio database is displayed.
After the database updation completes, click Next.
...
Step 9: On the Finalizing Migration screen, the project migration progress is displayed.
After the project migration completes, click Next.
...
Step 10: On the Project Migration Summary screen, the confirmation message displays that project migration is completed.
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”Migrated Successfully”.
Step 11: Click Finish to exit the Project Migration Utility.
| Info |
|---|
You must manually check in the migrated project folders present in the version control system that you use. |
Post Migration
...
Steps
After migrating the projects, in the Qualitia Automation Studio 8.0.x, you need to do the following:
Recreate the missing artifacts (Test case and tasks) in Qualitia Automation Studio 8.0.x. that you skipped during the project migration.
Recreate the custom actions, which were replaced by a dummy custom action.
Recreate the offline suites. For more information, refer to Offline PackageThe old offline suites cannot be executed through Qualitia Offline Jar file .