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.01.x.

Info

You can upgrade to QAS v8.01.x without uninstalling QFD. Also, QAS 8.01.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.01.x server must be installed before you start the QFD project migration.

  • QAS 8.01.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.01.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:

  1. Open the Qualitia Installation Package.

  2. Under the QualitiaProjectMigrationUtility folder.

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

Performing the Project Migration Process

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

...

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

  2. Click Next.

    Image RemovedImage Added

Step 4: On the Missing Artifacts Validation screen, review the information, and click Next.

...

Info

If you click Next, you go ahead only with those projects that were successfully verified.

...

Step 6: Onthe Qualitia 8.0 1 Database Details screen, enter the following details,and click Next.

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

  • Server: Port: Specify the QAS v8.01.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.01.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.01.x database.

  • Password: Specify the password for authentication.

  • Project Path: Specify the folder where Qualtia v8.01.x saves the project artifacts (test cases, tasks, and custom actions). 

    Image RemovedImage 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.

...

Step 8: On the Updating Database to Qualitia 8.01 screen, the progress of updating the new XML schema to the Qualitia Automation Studio database is displayed.

...

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.01.x, you need to do the following:

  • Recreate the missing artifacts (Test case and tasks) in Qualitia Automation Studio 8.01.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 .

...