Upgrading from Qualitia Automation Studio (QAS) for Web and Mobile 5.x, 6.x, or 7.x version to Qualitia Automation Studio v8.3.x includes the following steps:
Upgrade the QAS Server and QAS Client.
Migrate all the projects created in the previous versions to ensure that the old test cases and tasks are compatible with QAS v8.3.x. QAS client v8.3.x does not support the projects that are not migrated successfully.
Upgrading Qualitia Server and Client
Applying product updates will give you an enhanced experience of working with Qualitia Automation Studio.
Prerequisites
Qualitia WebDriver 5.x or above
It is strongly recommended to backup Qualitia server databases (Master, Project, and Result Databases).
If MySQL database server is installed on Linux machine, ensure that the values of column ProjectName and ProjectDBName names are in the lowercase under Master Project database in the table tblprojects. Entering project names in uppercase may cause failing upgrade process.
Ensure port 8887 and 8889 are open and accessible from the machine where you are installing Qualitia Server.
If the number of projects to be upgraded is more than 50, increase the max_connections limit from MySQL database configuration settings. For more information about increasing the limit, refer to Qualitia Troubleshooting section.
Close all the instances of Qualitia Automation Studio and Internet Explorer before starting the upgrade process.
If Qualitia Automation Studio is open, the upgrade process closes all the active Qualitia instances. If you have multiple Qualitia instances open, ensure to save the changes and close all the Qualitia instances before starting the upgrade process. For a detailed list of prerequisites, refer to the Prerequisites and Configurations section.
Upgrading the Qualitia Server
Note: Ensure that you take back up for all the projects. You need to restore the backup of the projects that failed to upgrade.
To update the Qualitia Server:
Ensure you have the valid product license activated for Qualitia.
Log on to the machine where Qualitia Server is installed and copy the QualitiaWDServer.exe to this machine.
Right-click QualitiaWDServer.exe and select Run as administrator.
The Welcome to the Qualitia Setup Wizard screen appears.
Do one of the following:
To upgrade the Qualitia Server, click Next.
To cancel the upgrade process, click Cancel.
It is recommended to use the updated product versions applying available product updates for seamless user experience.
All the database server details appear. All these fields are displayed in non-editable mode, click Next.
Click Next and you will see the master database name.
Select the Enable Dashboard option, if you want to enable Dashboard functionality.
For more information about the dashboards functionality, click here.Enabling this option, Qualitia consumes an additional database (except master and project databases) for managing data related to the dashboard functionality. Kindly make a note of it.
Enter the desired Dashboard Database name and click Next.
If you are upgrading from a previous QAS version to v8.2.x where some projects are integrated with TFS/Azure DevOps and their Test Case template file in the latest version of Qualitia have changed, the linked test cases metadata files are automatically upgraded to their latest versions. You can view the TFS/Azure DevOps integrated projects that are upgraded, and click Next.
The Project Details screen appears. You can view the projects selected for upgrade. Click Next.
Note: The projects for which the specified database user credentials lack some database privileges are highlighted in the red color as shown in the following figure:
Specify the Result Path to store results of the test cases executed outside Qualitia and click Next.
Qualitia uses this folder to store results of test cases executed through CI Tools (Jenkins, TeamCity, Bamboo), Build / Release Cycles from TFS/Azure DevOps, and offline package.
All the Qualitia clients should have read access to this directory.
Click Upgrade as shown in the following figure:
The Upgrade screen shows the upgrade progress for each project as shown below:
You can do the following actions:
Click Save Report to save the upgrade status of every project as an HTML file. After the report is saved, it opens automatically.
Click Show Logs to view the logs.
If some projects fail to upgrade, restore their backup, and then restart the upgrade process for them.
After all the projects are upgraded successfully, click Finish to exit the setup.
Upgrading the Qualitia Client
Once the administrator has updated Qualitia Server, other Qualitia users can update respective clients.
Note: Close all the Internet Explorer instances and do not open them during the Qualitia Client upgrade process.
To update Qualitia Client:
Log on to the machine where you want to upgrade Qualitia client.
Copy the QualitiaWDClient.exe from the update package to the machine.
Double-click the QualitiaWDClient.exe to start the update process.
Double click the QualitiaWDClient.exe to start the Qualitia Client update process.
After the upgrade process is completed successfully, click Finish.
Migration Process for Web/Mobile Projects
Points to Know
If you are using Qualitia v7.3.0 or above, there is no need to migrate projects.
The following are two ways for migrating the projects:
Using Project Migration Utility: Qualitia provides a Utility to migrate multiple projects in a single instance.
Using Qualitia Client: From Qualitia v7.3.0, if you select a non-migrated project, an error message is displayed in Qualitia that prompts you to migrate the selected project only. Upon clicking Migrate Now on this message, Qualitia guides you for migration of the selected project only.
In each screen of the migration process, you have an option to go to the previous screen or cancel the migration process at any time.
Any user having database and version control tool credentials can run the Project Migration Utility.
Recommendations for Project Migration
Latest versions of test cases and tasks must be available in the Project path
The Qualitia database is accessible
Migration process might take 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
Also, the migration process completes faster if other programs are not running on the machine.
Launching the Project Migration Utility
To launch the Project Migration Utility:
Open the Qualitia Installable.
Under the QualitiaProjectMigrationUtility folder, unzip the QualitiaProjectMigrationUtility.exe through 7-Zip file archiver only.
Execute the QualitiaProjectMigrationUtility.exe
Migrating Projects
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: Open the Qualitia Project Migration Utility.
On the Welcome to Qualitia Project Migration screen, review the recommendations, and click Next.
Click Next.
Step 2: On the Master Database Configurations screen, enter the following details, 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 selected SQL 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: Specify the 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.
Step 3: On the Project Selection screen, select the projects that you want to migrate now, and click Next.
Step 4: On the Version Control 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.
In the case of multiple projects, the version control details are entered for every project one-by-one.
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:
Tasks with missing XML files: Displays the missing tasks.
Test Cases with missing XML files: Displays the missing tasks.
Test Cases Impacted due to the deletion of tasks: 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.
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, and click the Refresh button. The Utility screen updates the missing tasks and test cases.
Click Next.
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.
Step 7: The Project Health Check screen starts for each selected project as shown in the following figure:
Verification for a project can 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 a project are locked by users.
The DB connection was interrupted.
Step 8: If verification fails for a project, click Corrective Actions to delete any test case or task file.
The Utility shows the problem in the test case or task XML file due to which verification failed.
Select the test case or task, and click Delete.
From the Project Health Check screen, click Retry to start the verification of that project.
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.
In the case of multiple projects:
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.
Click Next to start the Project Migration process.
Step 9: On the Project Migration Progress screen, the project migration progress is displayed.
After project migration completes, click Next.
Click Next.
Step 10: On the Project Migration Summary screen, 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”.
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.3.x.
Delete the DBCache folder, which is located at the following location:
%localappdata%\Qualitia\WD\Client\Settings\<Project Folder>\DBcacheRecreate all the offline packages created using old Qualitia versions
If any project is integrated with TFS/Azure DevOps, then re-publish the test cases associated with TFS/Azure DevOps test cases.