Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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.

Launching the Project Migration Utility

To launch the Project Migration Utility:

  1. Open the Qualitia Installable.

  2. Under the QualitiaProjectMigrationUtility folder, extract the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.

  3. 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.
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, do the following:

  1. Select the QFD projects you want to migrate.

  2. 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 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, do the following:

  • Click Corrective Actions to delete any test case or task file having technical problems.

  • Click Custom Actions to add dummy VB files for the missing VB files.

Select the test case or task, and click Delete.

From the Project Health Check screen, click Retry to start the verification of that project.

The Utility shows the problem in the test case or task XML file due to which verification failed.

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: Enter the database details for the Qualitia Automation Studio to which you want to migrate.

Step 10: The Project Migration process starts as shown in the following figure:

After the migration completes, 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

  • You need to recreate offline suites using the offline package. For more information, refer to Offline Package

  • No labels