QTP vs TestComplete vs Selenium



Feature	QTP(11.5 /11)	Selenium(2)	TestComplete(10)
Language Support	VB Script	Java, C#, Ruby, Python, Perl	VBscript, Jscript, Delphi Script and many other.
Windows (Non-browser) based Application support	Yes	PHP , Javascript	Flex, WPF, grids and other controls --NET (Windows Forms), WPF (XAML), Visual C++, Visual Basic, Borland Delphi, C++Builder, Java, JavaFX, Visual FoxPro, Sybase PowerBuilder
Browser support	Google Chrome (uptill ver 23) Internet Explorer , Firefox ( ver 21)	Google Chrome , Internet Explorer , Firefox , Opera , HtmlUnit	IE,Support for Opera 17-8, Chrome 31, Firefox 24-26(Web and Rich Internet Application Testing)
Environment Support	Only Windows	Windows , Linux , Solaris OS X , Others (If brower & JVM or Javascript support exists)	Support for Win 64-bit applications
Mobile (Phones & Tablets) support	Different commercial product i.e. HP UFT Mobile (formerly known as MobileCloud for QTP)	Android , iPhone & iPad , Blackberry , Headless WebKit	Windows Desktop and Client/Server, Web, and Mobile. Source,Android platform support,iOS platform support
Framework	Easily integrated with HP Quality Center or HP ALM (separate commercial products)	Selenium + Eclipse + Maven / ANT + Jenkins / Hudson & its plugins / Cruise Control + TestNG + SVN	Enchance tests using external functions Calling DLL and Windows API functions, using .NET and Java classes ,Data Driven testing-Integrated support for data-driven testing and a built-in test data generator
Continuous Integration	Possible through Quality Center / ALM or Jenkins	Possible through Jenkins / Hudson / Cruise Control	Coverage testing with AQtime integration ,Tracing critical failures in applications with AQtrace integration Tracing exceptions, freezes and crashes in the application under test    ,Integration into Visual Studio 2013 and Team Foundation Server 2013.
Object Recognition / Storage	Inbuilt Object Repository (storing Element Id, multiple attributes) along with weightage that gives flexibility on deviation acceptance in control recognition	UI Maps and different object location strategy such as -XPath Element ID or attribute DOM	Object Recognition is doing by two way1) Default Object Naming2)Name Mapping
Image based Tests	Easily possible	strategy such as -XPath Element ID	Need workaround
Reports	Quality Center has in-built awesome dashboard	possible through testng/junit ,need workaround	in-Build report or customised is possible
Software Cost	License & Annual maintenance fees	Zero
Coding Experience of Engineer	Not Much	Should be very good along with technical capabilities of integrating different pieces of framework
Script Creation Time	Less	High
Hardware resource (CPU + RAM) consumption during script execution	High	Low
Product Support	Dedicate HP support along with support forums	Open Source Community