Versions Compared

Key

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

...

Migrating Projects

Step 1: Launch the The Welcome to Qualitia Project Migration Utility screen opens showing the pre-requsities.
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: Lets you select the database type, MySQL or SQL Server.

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

  • Database Name: Lets you specify the Master Database name.

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

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

  • Password: Lets you specify the password for authentication.

  • Version Tool: Select as SVN or None.

  • Project Path: Lets you specify the path where Qualitia saves the project artifacts (test cases and tasks).

...

Step 3: Under The QFD Project Selection , do screen opens.

Perform the following steps:

  1. Select the QFD projects 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 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.
    Perform the following steps:

    • Do one of the following:

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

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

Note

If you skip the missing filesartifacts for a project, the migrated projects will not have the missing test cases and tasks.

...

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 starts has started for each the selected projectprojects.Image Removed

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.

...

Step 6: The Verification of Project Artifacts shows screen opens toshow whether verifications failed in test cases and tasks XML file for every project.

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

  1. (Optional) Click Download Report to view the verification status of each test casescase, 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, you can view the reason for a test case or task verification failure.

  2. Click Corrective Actions to delete test cases or task files having technical problems.Click Custom Actions 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 Project directory. Also, if you see some artifacts do not have much impact, you can select them, and click Delete to remove them.

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

  4. Click Retry after After updating the project artifacts, click Retry to re-verify the project artifacts.

...

  1. Click Next to start the Project Migration process.

...

Step 8: The Qualitia 8.0 Database details 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: 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.

      Image Added


Step 9: If you have taken the backup, then backup for the selected QFD projects start.

After project backup completes, click Next.

...

Step 9: If you have taken the backup, then project restore starts to apply new XML schema in the Qualitia Automation Studio database.

After project backup restore completes, click Next.

...

Step 10: The project migration starts.

After project migration completes, click Next.

...

Step 11: 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”.

...

Post Migration Considerations

  • If you had skipped any artifacts, you need to recreate them in Qualitia Automation Studio 8.0.0.

  • If you have added a dummy custom action VBS file, you need to re-create the VBS file.

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

...