...
| Info |
|---|
Project Migration using Qualitia Client If you are migrating a single project from a Qualitia client, there is no need to enter database or version control details. If some project artifacts do not match with version control, Qualitia directly opens the details of artifacts missing screen, as described in step 5. Else, it directly displays the Project Health Checkup screen as described in step 6.. |
Step 1: Launch Open the Qualitia Project Migration Utility, the first screen opens as shown in the following figure:.
On the Welcome to Qualitia Project Migration screen, review the recommendations, and click Next.
...
Click Next.
Step 2: Enter On the Master Database Configurations screen, enter the following database details.
...
Field
...
Description
...
Database Type
...
Select the Server from the drop-down list: SQL Server and MySQL.
...
Server Port
...
Enter the Server and the Port IDs.
The default port is 3306 for MySQL and 1433 for SQL.
...
Authentication
...
Select the authentication type: Windows Authentication or SQL Server Authentication
This field is applicable for SQL server only.
...
User Name
...
Enter the database server username
...
Password
...
Enter the database server password.
...
Database Name
...
Enter the database name which contains metadata of all the projects.
...
Qualitia Server URL
...
, and click Next.
Type: Select the database type of Qualitia database, MySQL or SQL Server.
Server: Port: Specify the Qualitia 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 the Qualitia database.
Authentication: If you have selectedSQL Server database, select this option to authenticate to the SQL Server using Windows credentials.
User Name: Specify the username to connect to the Qualitia database.
Password: Specify the password for authentication.
Qualitia Server URL: Specifythe URL where Qualitia Server is installed.
The Qualitia Server URL is a combination of
...
the hostname/IP and port 8887 where you have installed Qualitia server.
For example, http://192.112.33.123:8887.
By default, Qualitia uses port 8887. You may change it while installing Qualitia Server component.
...
Click Next.Step 3: Select projects to migrate from the Projects Selection screen On the Project Selection screen, select the projects that you want to migrate now, and click Next.
...
Click Next.
Step 4: Enter On the Version Control details for the selected project.
...
Field
...
Description
...
Version Control
...
Select the version control tool you are using for managing Qualitia project artifacts (Tasks and Test cases).*
...
SVN Client
...
screen, enter the following details, and click Next.
Version Tool: Select SVN, GIT or None.
SVN Client: If you select SVN, select the SVN client version from the drop-down list. This option is available for SVN only.
User Name
...
: Enter the user name to connect to the version control server.
Password
...
: Enter the
...
password to connect to the version control server.
| Info |
|---|
In the case of multiple projects, the version control details are entered for every project one-by-one. |
...
Click Next.
Step 5: If some test cases or tasks are missing for some projects, then the following are Step 5: On the Missing Artifacts Validation screen, review the information, and click Next.
For every project it shows the results for the following three types of validation errors highlighted for those projects:
Tasks with missing XML files: Shows Displays the total number of tasks and name of each task that is missingmissing tasks.
Test Cases with missing XML files: Shows the total number of test cases and name of each test case that is missing Displays the missing tasks.
Test Cases Impacted due to the deletion of tasks: Shows number and name of Displays the test cases which are affected due to that are associated with the missing tasks.
...
Remarks: Displays if all the necessary artifacts are available. Click Next if all the artifacts are available.
Perform the following steps if any of the artifacts are missing:Find and add the missing test case/task XML files
...
in their
...
associated project folders
...
If files are not found, click Next to delete them.
...
, and click the Refresh button.The Utility screen updates the missing tasks and test cases.
Click Next.
| Info |
|---|
You can skip the missing artifacts for a project if you are unable to find some missing tasks and test cases. After the project is migrated, you need to re-create the missing tasks and test cases. |
...
Step 6: The Project Migration Utility takes backup of the validated project artifacts, as shown in the following figure:
...
Click Next to start the Project Migration process.
Step 9: The On the Project Migration process starts as shown in the following figure: Progress screen, the project migration progress is displayed.
After project migration completes, click Next.
...
Click Next.
Step 10: When a On the Project Migration Summary screen, the confirmation message displays that project migration is successful, the number of test cases and tasks are displayed along with their names, as shown in the following figure:
...
If 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”.
Step 11: Click Finish to exit the Project Migration Utility.
...
Post Migration Considerations
After migrating a project, you must perform the following operations:
While the project migration, if you have skipped any missing artifact, you need to recreate them in Qualitia Automation Studio 8.0.x.
Recreate all the offline packages created using old Qualitia versions
If the project is integrated with TFS/Azure DevOps, then re-publish the test cases associated with TFS/Azure DevOps test cases.
...