Versions Compared

Key

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

...

  • Qualitia recommends that you run the QFD Migration Utility on any of the Qualitia client machines. The Ensure that the selected Qualitia client machines machine already have the prerequisites for running the utility and the project folders are integrated with version control systems (SVN) are also available on them.

  • 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

    • SVN (if it is integrated with QFD)

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

...

Info

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

...

  1. Click Download Report to 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 are unable to 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.

...

Step 7: On the Generating Database Scripts for Migration screen, the 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.
The following confirmation message appears:

...

Step 9: On the Finalizing Migration screen, the project migration progress is displayed.

After the project migration completes, click Next.

...

Info

You must manually check in the migrated project folders present in to 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. While that you skipped during the project migration, if you have added .

  • Recreate the custom actions, which were replaced by a dummy custom action, you need to develop the custom action.

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