Qualitia For Desktop Architecture

Open

Licensing Service

Qualitia licensing service uses port 1947 to connect Qualitia Server and Qualitia Clients. It is mandatory to keep this server up and running and connected to the network all the time. You can install this component on the same machine where Qualitia server is installed or you can use a separate machine/system to install it.

Qualitia Web Server

Qualitia Web Server is a server-side component for providing multiple functionalities to clients such as Qualitia Clients, Object Spy, and so forth. Also, it helps in rendering MS Excel-based dashboards and runs integration services for TFS/Azure DevOps. It uses port 8887, however, you may choose to use the different port at the time of Qualitia Server installation.

Database Server

Qualitia For Desktop users SQL database servers to store its test artifacts and test-related data. Qualitia For Desktop supports MS SQL or MySQL to store the data. You can use any of these two to work with Qualitia. As shown in the diagram, Qualitia uses port 1433 to connect to the MSSQL database and port 3306 to connect to the MySQL database. Port numbers may differ in case you have changed them at the time of installation. This database can be installed on the same machine/system where Qualitia Server is installed or you can use a different machine/system to install these databases. You can install Qualitia clients on different machines and connect them to these database servers which are installed centrally in the network. It is important to make these servers accessible to the systems where Qualitia clients are installed.

UFT

Qualitia uses a product of HP in the backend, which is Unified Functional Testing (UFT), to identify objects.

Object Repository

The objects captured are saved in a tsr file, which again is saved in the Qualitia database.

UFT Execution Engine

Qualitia for Dekstop in the backend uses the UFT execution engine to execute its test cases.

CI/CD Tools

Qualitia for Desktop seamlessly integrates with Team City, Jenkins, and Bamboo for Continous Integration/ Continous Delivery process.