QTP Versus Selenium
When it comes to test automation tools
for web application testing it is hard to choose between the available options
in the market and the right alternative that offers best of the latest
technologies from the market place at the right budget. Open source tools
provide the benefit of low initial investment but, they’re not always the best
alternative in the long run due to lack of official support & training.
Commercial tools on the other hand are highly expensive to implement resulting
in higher cost of failure should the right tool not be selected.
Automation
is a continuous process and it’s very important to have the basics right:-
1.
Setting up the test environment
2.
Screening the available tool
options
3.
Creating a Proof of Concept with a few
sample test scenarios for the application
4.
Preparing (automation) frameworks
5.
Building libraries of functions &
methods
6.
Defining configuration parameters
To
help test managers and automation engineers choose the right alternative, we
have prepared a comparison matrix between the three closest contenders that are
highly rated by Test Managers and Automation Engineers alike. Here is a
comparison between HP QTP with Selenium.
HP
QTP 10
|
Selenium
|
|
Programming
knowledge required?
|
Yes
|
Yes
|
Learning
curve to be productive
|
3-4
months
|
2-3
months
|
Record
& Playback
|
Can
only be used in Microsoft Internet Explorer
|
Selenium
IDE to be used
|
Data
Driven Testing
|
Complex
VB Scripting required
|
Requires
Extensive Coding
|
Database
Support
|
With
the help of DSN (ODBC32 Interface)
|
Requires
Extensive Coding
|
Object
Repository
|
Official
term is Window declarations. They can be edited directly from the Editor
|
Non
Editable
|
Test
Case
|
Termed
as Testcase. Each Testcase has block of coding statements.
|
Termed
as Automation Script
|
Language
Support
|
VBScript
|
Selenese,
Java, Ruby, Perl, PHP, Python, C#, Groovy
|
Functional
Testing, Load Testing, Service Monitoring from one test script
|
Complex
code required
|
Not
Available
|
Run
tests in the Cloud, in your QA lab, or both
|
Yes
|
Yes
|
Results
Reporting
|
Results
are stored into *.res binary files. It can be converted into different
formats. Multiple versions can be stored into single file.
|
Basic
Reporting
|
Defect
Management Integration
|
In
Built Defect Reporting
|
Not
Available
|
OS
Platform Support
|
Windows
Only
|
Only
stable on Windows & Linux
|
Test
Management Integration
|
HP
Quality Center
|
Not
Available
|
Scheduled
execution
|
No
|
Yes,
but with complex code
|
No comments:
Post a Comment