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 35 Next »

The Project artefacts created in Qualitia for desktop must be compatible with Qualitia Automation Studio v8.0.0. Qualitia has provided a QFD Project Migration Utility to migrate the QFD projects to Qualitia Automation Studio v8.0.0.

Rules and Recommendations for Project Migration

  • QAS v8.0.0 must be installed with the same database management system that QFD is using.

  • Upgrade your QFD to v4.3.11.

  • Ensure that you must have access to:

    • QFD database

    • SVN if it is integrated with QFD

    • QAS 8.0.0 database

  • The project path must be updated with the latest versions of test cases and tasks.

  • Plan the migration process as it might take more time for large projects.

  • 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

Performing the Project Migration Process

The Utility performs the project migration in the following three phases:

  1. Finding the missing projects artifacts for the selected projects

  2. Conducting Health Check on the selected projects

  3. Starting the Project Migration for the selected projects

To migrate the projects:

Step 1: The Welcome to Qualitia Project Migration screen opens showing the recommendations and migrations.
From the first screen, click Next.

Step 2: The Qualitia for Desktop (QFD) Database/Version Control Information screen opens.

Enter the following details to connect to the QFD database.

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

  • Authentication: To authenticate the SQL Server using Windows credentials. 

  • User Name: Specify the username to connect with the QFD database.

  • Password: Specify the password for authentication.

  • Version Tool: Select as SVN or None. If you select SVN, enter your SVN username and password to authenticate SVN connection.

  • Project Path: Specify the path where QFD saves the project artifacts (test cases and tasks).

  • Backup database before migration: To take the backup of selected QFD projects while migrating the projects start. You can skip this option if you have already taken the backup for the selected project.


Step 3: The QFD Project Selection screen opens.

Perform the following steps:

  1. Select the QFD projects you want to migrate.

  2. Click Next.

Step 4: The Missing Artifacts Validation screen opens.

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.

  • Remarks: Shows the missing data other than tasks and test cases in every QFD project.

    Perform the following steps:

    • Do one of the following:

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

      • Skip the missing test case and task files, and click Next.

If you skip the missing artifacts for a project, after the project migrates, you need to re-create the missing tasks and test cases.

​Step 5: The Conducting Project Health Check screen opens.

You can see that Project Health Check has started for the selected projects. The utility verifies whether any data is missing from the database, and test cases and tasks in Project Path are correct.

The project health checkup may fail due to the following reasons:

  • The number of Test cases in the Project Database and Project path is not equal.

  • Some test cases of the project are locked.

  • If the connection to DB is interrupted.

If verification is successful for all the projects, click Next.

If verification fails for a project, perform the following steps:

  1. (Optional) Click Download Report to view the verification status of each test case, tasks, and custom action VB files along with their IDs. Also, you can view the reason for a test case or task verification failure.

  2. Click Corrective Actions to know the problems of each test case and tasks for which verifications failed.
    You can update the test case and tasks manually by opening through the Project directory. Also, if you see some artifacts that do not have much impact, you can delete them.

  3. Click Custom Actions to work around the custom actions for which verifications failed, and then click Create Script to add dummy VB files for the missing VB files.

  4. After updating the project artifacts, click Retry 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.

  1. Click Next to start the Project Migration process.

Step 8: The Qualitia 8.0 Database Details screen opens to configure the database details.

  1. Enter the following database details for the Qualitia Automation Studio to which you want to migrate.

    1. Type: Select the database type for QAS v8.0.x, MySQL or SQL Server.

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

    3. Database Name: Specify the Master Database name of QAS v8.0.x.

    4. Authentication: To authenticate the SQL Server using Windows credentials. 

    5. User Name: Specify the username to connect with the QAS v8.0.x database.

    6. Password: Specify the password for authentication.

    7. Project Path: Specify the folder where Qualitia project artifacts (test cases, tasks, and custom actions) for QAS v8.0.x are saved. 

Step 9: The Generating Database Scripts for Migration screen opens to generate database scripts for migration. Also, if you have selected to take the database backup, it takes the backup of selected projects present in the QFD database.

After project backup completes, click Next.
A confirmation message displays, which indicates that if you cannot revert and interrupt the migration process, the migrated project in Qualitia Automation Studio is unusable.

Do one of the following:

  • Click Yes to start the migration.

  • Click No if you want to migrate later on at your convenience.

Step 9: The Updating Database to Qualitia 8.0 screen opens and shows that Utility is applying the new XML schema in the Qualitia Automation Studio database.

After project restore completes, click Next.

Step 10: The Finalizing Migration screen opens to shows the project migration progress.

After project migration completes, click Next.

Step 11: The Project Migration Summary screen 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

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

  • While the project migration, if you have added a dummy custom action VBS file, you need to do the required coding in the migrated VBS file.

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

  • No labels