The Project artefacts created in Qualitia for desktop must be compatible with Qualitia Automation Studio 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. |
Rules and Recommendations for Project Migration
Upgrade your QFD to v4.3.11Qualitia 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 must have access to:
QFD database
Version Control, SVN (if it is integrated with QFD project artifacts)
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 GBfor 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:
Open the Qualitia InstallableInstallation Package.
Under the QualitiaProjectMigrationUtility folder, extract .
Extract the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.
Execute the QualitiaProjectMigrationUtility.exe
Performing the Project Migration Process
The Utility performs the project migration in the following three phases:
Finds Finding the missing projects project artifacts in for the selected projects
Conducts Conducting Health Check on the selected projects
Starts Starting the Project Migration for the selected projects
To migrate the projects:
Step 1: The Open the Qualitia Project Migration Utility.
On the Welcome to Qualitia Project Migration screen opens showing , review the recommendations and migrations.
From the first screen, , and click Next.
...
Step 2: The On the Qualitia for Desktop (QFD) Database/Version Control Information screen opens.Enter , enter the following details to connect to the QFD database, and click Next.
Type: Lets you select Select the database type of QFD database, MySQL 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 authenticate connect to SVN connectionserver.
Project Path: Lets you specify the path 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: The On the QFD Project Selection screen opens.Perform , do the following steps:
Select the QFD projects that you want to migrate.
Click Next.
Step 4: The On the Missing Artifacts Validation screen opens, 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.
Do one
Perform the following steps :if any of the
followingartifacts are missing:
Find and add the missing test case/task XML files in their
associated project folders, and click the Refresh button.
The Utility screen updates the missing tasks and test cases.
Click Next
.
| Noteinfo |
|---|
If you You can skip the missing artifacts for a project , after if you are cannot find some missing tasks and test cases. After the project migratesis migrated, you need to re-create the missing tasks and test cases. |
...
Step 5: The On the Conducting Project Health Check screen opens.You can see that Project Health Check has started , the project health check starts for the selected projects. The QFD Migration Utility verifies whether all the project artifacts for each project are correct and then generates a Health Check report as an HTML file.
| Info |
|---|
The project health checkup may fail due to the following reasonsif:
|
If Click Next, if the health check verification is successful for all the projects, click Next.If
Perform the following steps, if the verification fails for a project, perform the following steps:
...
any project due to incorrect or missing project artifacts.
Click Download Report to view the verification status of each test case, tasks, and custom action VB files along with their IDs. Also, you can view the reason for a test case or task verification failure.
Click Corrective Actions to 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 the Project directory. Also, if you see some artifacts do not have much impact, you can select them, and click Delete to remove them.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 filesdownload the Migration Health Check report.
In the Migration Health Check report, click Test Cases and Tasks sections to know the test cases and tasks that are incorrect.
To resolve the validation issues, fix the incorrect test cases and tasks manually.
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.
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:Remove the duplicate custom actions.
For the missing custom actions, find and add them to the Project Path.
On the QFD Migration Utility, click Custom Actions to work around the missing actions if you are unable to resolve them.
Click Create Script to create dummy custom actions with empty methods for each missing custom action.
After updating the project artifacts, click Retry to re-verify the project artifacts.
| Info |
|---|
You can migrate only those projects which were successfully verified. |
Click Next to start the Project Migration processperform the health check on the projects again.
Do one of the following:
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.
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 86: TheOnthe Qualitia 8.0 Database Details screen opens to configure the database details.
...
, enter the following
...
details,and click Next.
Type:
...
Select the database type for QAS v8.0.x, MySQL 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).
Step 97: The On the Generating Database Scripts for Migration screen opens to generate , the progress of generation of database scripts that are required for migration is displayed. Also, if If you have selected opted to take back up the database backup, it takes the in step 2, then a backup of the selected projects present is created in the QFD database.
After the project backup completes, click Next.
A The following confirmation message displays, which indicates that if you cannot revert and interrupt the migration process, the migrated project in Qualitia Automation Studio is unusable.
Do one of the following:
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 98: The On the Updating Database to Qualitia 8.0 screen opens and shows that Utility is applying , the progress of updating the new XML schema in to the Qualitia Automation Studio database is displayed.
After project restore the database updation completes, click Next.
...
Step 109: The On the Finalizing Migration screen opens to shows , the project migration progress is displayed.
After the project migration completes, click Next.
...
Step 1110: The On the Project Migration Summary screen opens, 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 utilityProject 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.0.While x. that you skipped during the project migration, if you have added .
Recreate the custom actions, which were replaced by a dummy custom action VBS file, you need to do the required coding in the migrated VBS file. You need to recreate offline suites using the offline package.
Recreate the offline suites. For more information, refer to Offline Package .