Versions Compared

Key

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

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.
However, Qualitia recommends uninstalling QFD after migrating all the projects to avoid confusion.

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 and version control, and to :

    • QFD database

    • SVN (if it is integrated with QFD)

    • QAS 8.0.

    0
    • x database

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

  • The Plan the migration as the process might may 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 more time for large projects.

  • For a better turn-around time .

    RAM - 16 GB

    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 - 5GB

...

    • or more

  • Close all the programs for better performance

Launching the Project Migration Utility

To launch the Project Migration Utility:

  1. Open the Qualitia InstallableInstallation Package.

  2. Under the QualitiaProjectMigrationUtility folder, extract .

  3. Extract the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.

  4. Execute the QualitiaProjectMigrationUtility.exe

...

Performing the Project Migration Process

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

  1. Finding the missing project 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: Launch Open the Qualitia Project Migration Utility.From the first screen,

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

...

Step 2:Enter On the Qualitia for Desktop (QFD) Database/Version Control Information screen, enter the following details to connect to the QFD database, and click Next.

  • Type: Lets you select Select the database type of QFD databaseMySQL or SQL Server.

  • Server: Port: Lets you specify the 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: Lets you specify Specify the Master Database name of the QFD database.

  • Authentication: Lets you authenticate If you have selectedSQL Server database, select this option to authenticate to the SQL Server using Windows credentials. 

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

  • Password: Lets you specify  Specify the password for authentication.

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

  • Project Path: Lets you specify the path where Qualitia 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: Under On the QFD Project Selection screen, do the following:

  1. Select the QFD projects that you want to migrate.

  2. Click Next.

...

  1. Image Added

Step 4: The Utility validates whether all the tasks and test cases in the project path are present 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 missing tasks that are missing .

  • Test Cases with missing XML files: Shows Displays the test cases that are missing tasks.

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

    Do one

    if any of the

    following

    artifacts are missing:

    To
    1. Find and add the missing test case/task XML files

    : Find and add them
    1. in their

    respective
    1. associated project folders

    .
    1. , and click the Refresh button.


    1. The Utility screen updates the missing tasks and test cases.

    To skip the missing test case and task files, click
    1. Click Next.

Noteinfo

If you You can skip the missing files, the migrated projects will not have the missing test cases and tasks.

...

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: The 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 selected project.Image Removedproject are correct and then generates a Health Check report as an HTML file.

Info

...

The project health checkup may fail

...

if:

  • The number of Test cases in the Project Database and Project path

...

  • is not equal.

...

  • Any of the test cases

...

  • in project are locked.

...

  • The connection to

...

  • the database is interrupted.

Step 6: 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 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.

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

  2. Click Corrective Actions to delete test cases or task files having technical problems.

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

  4. Click Retry after updating the project artifactsto re-verify the project artifacts.
Info

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: Qualitia 8.0 Database details screen opens.

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

    Type: Lets you select the database type

    download the Migration Health Check report.

  2. In the Migration Health Check report, click Test Cases and Tasks sections to know the test cases and tasks that are incorrect.

    1. To resolve the validation issues, fix the incorrect test cases and tasks manually.

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

  3. 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:

    1. Remove the duplicate custom actions.

    2. For the missing custom actions, find and add them to the Project Path.

    3. On the QFD Migration Utility, click Custom Actions to work around the missing actions if you are unable to resolve them.

    4. Click Create Script to create dummy custom actions with empty methods for each missing custom action.

  4. After updating the project artifacts, click Retry to perform the health check on the projects again.

  5. Do one of the following:

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

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

...

Take Database backup: Enables to take the backup of QFD projects.

Step 9: If you have taken the backup, then project backup starts.

...

...


  • Image Added

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.
Step 10: The project migration starts. After 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 1110: The On the Project Migration Summary opensscreen, 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”.

Click Finish to exit the project migration utility.

...

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