Summary -
In this topic, we described about the differences between Selenium and QTP in detail.
Below are the differences between Selenium and QTP -
Parameters | Selenium | QTP |
---|---|---|
License | Selenium is free open source. So, there will be no or less maintenance and testing cost. | License should be purchased to use QTP. |
OS compatibility | Android, iOS, Windows, Linux, Mac, Solaris. | only on Windows. |
Programming languages compatibility | Java, C#, Ruby, Python, Perl, PHP and JavaScript. | VB Script. |
Works on IDEs | Eclipse, .Net, NetBeans, etc. | QTP developed IDE. |
Repository | Does not have an object repository of its own. | Its own object repository available. |
Environment | Allows all additional plugins. | Supports SAP, Oracle without any add-ons support. |
Testing Applications | Selenium is only for testing web-based apps | Selenium is only for testing web-based apps. |
Cloud Execution Model | QTP’s one-script/one-machine execution model cannot get efficient use of distributed test execution via cloud-based infrastructure. | Selenium-Grid is exclusively designed to run concurrent tests on different machines using different browsers and different operating systems in parallel. So perfect match for cloud-based testing architectures and services |
Execution Efficiency | QTP tests one application per machine. | Selenium can execute multiple, simultaneous tests on a single machine. |
Browser Compatibility | Selenium is compatible with 9 different types of browsers of which two are headless browsers such as chrome, IE, Firefox, Safari, Android, Opera, HtmlUnit, Phantom JS etc. | QTP is compatible with only 4 specific versions of browsers such as chrome, IE, Firefox and Safari. |
Customer Support | supported by active user community and no dedicated support team available. | Dedicated HP technical support for QTP. |
AUT Technology | HTML5 & Web2.0 | visual basic ,HTML 5 , web 2.0, Active, SAP, QT etc. |
Test Management | No dedicated tool for tracking tests | Dedicated tool for tracking tests |
Resource utilization | Low resource utilization | High resource utilization |
Object Repository/Recovery | None. | Built-in object repository and recovery |
Browser Controls | None | Regular browser control can be used to control the application within the browser. |
Test Report Generation | External toll required to generate reports | Built-in test report generation available. |
Parameterization | Depends on the programming language | Built-in tools are available. |
Software Type | Set of APIs | Desktop based application. | Layers | Selenium can be used to test only the front end or interface layer. | UFT can be used to test all three layers of an application the interface, the service layer, and the database layer. | Coding Skills | Required | Not required much. |
Object Repository | Selenium has no such feature. | It comes with built-in Object Repository. |
Integrates | There is no such tool that integrates with Selenium. | HP UFT integrates with test management tool like HP Quality Center. |
Dialog box support | It supports dialog box partially. | All types of dialog box are supported by it. |
Scripting | It is a low-level tool with less functionality. Script requires more time to develop and maintain. | HP QTP is more user friendly and scripts are developed quickly. |
Backward Backward | New releases with API changes. So, scripts should be updated | Have good backward compatibility. Latest version of HP ALM supports the 5 years back code. |
Image Testing | Here, image testing can be done only with the help of Silkuli. | using QTP, image testing can be done perfectly as it has the feature to capture the images. |
Framework | selenium + Eclipse + Maven / ANT + Jenkins / Hudson & its plugins / Cruise Control + TestNG + SVN. | Easily integrated with HP Quality Center or HP ALM (separate commercial products. |