Versions Compared

Key

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

...

  • Latest versions of test cases and tasks must be available in the Project path

  • The Qualitia database is accessible

  • Migration The migration process might 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 better turn-around time.

    • RAM - 16 GB

    • Quad-Core Processor

    • Free Disk Space - 5GB

...

Info

Verification for a project may 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 the project are locked.

  • If the connection to DB is interrupted.

...

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

  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

...

  1. test

...

  1. cases or task

...

  1. files having technical problems.

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

Select the test case or task, and click Delete.

From the Project Health Check screen, click Retry to start the verification of that project.

...

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

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.

...

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

...

  • .

...

Step 9: Qualitia 8.0 Database details screen opens.

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

Step 10: The Project Migration process starts as shown in the following figure:

...

    1. Type: Lets you select the database type, MySQL or SQL Server.

    2. Server: Port: Lets you specify the 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: Lets you specify the Master Database name.

    4. Authentication: Lets you authenticate the SQL Server using Windows credentials. 

    5. User Name: Lets you specify the username to connect with the database.

    6. Password: Lets you specify the password for authentication.

    7. Project Path: Specify the folder where Qualitia project artifacts (test cases and tasks) are saved. 

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

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

After project backup completes, click Next.

Step 11: The project migration starts. After project migration completes, click Next.

...

Step 10: When a project migration is successful, the number of test cases and tasks are displayed along with their names, as shown in the following figure:

...

If The Project Migration Summary 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”.

Step 11: Click Finish to exit the Migration Utility.project migration utility.

...

Post Migration Considerations

...