Versions Compared

Old Version 3

changes.mady.by.user ravi.chandran

Saved on

compared with

New Version 4

changes.mady.by.user ravi.chandran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Points to Know

  • If you are using Qualitia v7.3.0 or above, there is no need to migrate projects.

  • 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, unzip the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.

  3. 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: Open the Qualitia Project Migration Utility.

On the Welcome to Qualitia Project Migration screen, review the recommendations, and click Next.

Click Next.

Step 2: On the Master Database Configurations screen, enter the following details, and click Next.

  • Type: Select the database type of Qualitia database, MySQL or SQL Server.

  • Server: Port: Specify the Qualitia 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 Qualitia 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 Qualitia database.

  • Password: Specify the password for authentication.

  • Qualitia Server URL: Specifythe 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: On the Project Selection screen, select the projects that you want to migrate now, and click Next.

Step 4: On the Version Control screen, enter the following details, and click Next.

  • Version Tool: Select SVN, GIT or None.

  • SVN Client: If you select SVN, select the SVN client version from the drop-down list. This option is available for SVN only.

  • User Name: Enter the user name to connect to the version control server.

  • Password: Enter the password to connect to the version control server.

Info

In the case of multiple projects, the version control details are entered for every project one-by-one.

Step 5: 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: Displays the missing tasks.

  • Test Cases with missing XML files: Displays the missing tasks.

  • Test Cases Impacted due to the deletion of tasks: Displays the test cases 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:

    1. Find and add the missing test case/task XML files in their associated project folders, and click the Refresh button.The Utility screen updates the missing tasks and test cases.

    2. Click Next.

Info

You can skip the missing artifacts for a project if you are unable to find some missing tasks and test cases. After the project is migrated, you need to re-create the missing tasks and test cases.

Step 6: The Project Migration Utility takes backup of the validated project artifacts, as shown in the following figure:

Image Modified


Click Next.

​Step 7: The Project Health Check screen starts for each selected project as shown in the following figure:

Info

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.

Info

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: On the Project Migration Progress screen, the project migration progress is displayed.

After project migration completes, click Next.

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”.

Click Finish to exit the Project Migration Utility.

Post Migration Considerations

After migrating a project, you must perform the following operations:

  • While the project migration, if you have skipped any missing artifact, you need to recreate them in Qualitia Automation Studio 8.0.x.

  • 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.