Quick Comparison of IBM RFT & HP QTP the leading Functional Testing Tools
The software testing community is aware of the emergence of IBM Rational Functional Tester (RFT) & HP QuickTest Professional (QTP) as the popular choice of testers & programmers for their functional testing needs.
First of all let us have a quick overview of both the software testing tools, before going into a broad comparison among the functionality of the two.
1) Quick Overview – IBM RFT:
RFT is a test automation tool used by quality assurance teams to perform automated regression testing. Testers create scripts by using a test recorder, which captures a user’s actions against their application under test. The recording mechanism creates a test script from the actions. The test script is produced as either a Java or Visual Basic.net application, and it is represented as a series of screen shots that form a visual storyboard. Testers can edit the script using standard commands and syntax of these languages, or by acting against the screen shots in the storyboard. Test
scripts can then be executed by Rational Functional Tester to validate application functionality.RFT provides us choice among two scripting languages and two development environments i.e. Java under Eclipse framework, alternatively Visual Basic.NET under Microsoft Visual Studio. One of the great plus point of RFT is that irrespective of the scripting language and the development environment deployed for development, we can easily integrate RFT with them while developing the tests for automation.
2) Quick Overview – HP QTP:
QTP is automated testing tool meant for performing functional and regression testing of various software applications and environments through a user interface like native GUI or web interface. It uses VBScript as the scripting language for specifying a test procedure, & for manipulating the objects & controls of the AUT. It supports a keyword and a powerful graphical user interface.
Now let us make a broad comparison among the two tools
|Sr.||What IBM RFT has||What HP QTP has|
|1||Certification exam is known as “Rational Functional Tester for Java” (Exam code � IBM 000-842)||Certification exam is known as “HP AIS Functional Testing v11.x Software” (Exam code � HPO M47)|
|2||Certification Exam details:
# Number of questions � 54
# Type of Question: multiple choice.
# Exam time: 75 minutes
# Passing score: 60%
|Certification Exam details:
# Number of questions – 72
# Type of Question: multiple choice, drag-and-drop, and point and click
# Exam time: 105 minutes
# Passing score: 75%
|3||Sections & objectives of certification exam:
1) ENV (navigation, configuring and enabling environments, test project, preferences)
2) REC (recording process, insert recording, script support functions)
3) VP (verification points)
4) PLY (play back, testing the test, regression testing, use of comparators)
5) LOG (types of logs, logging options, use of comparators)
6) EXT (extending scripts, modifying scripts, components of script)
7) OBJ (test object maps, pattern-based recognition, controlling recognition)
8) DAT (data-driven testing, creating and editing datapools)
|Sections & objectives of certification exam:
1) Automated test planning
2) Basic test creation and how QTP works with objects
3) Basic test verification and enhancement
4) Modular automated test builds
5) QTP and ALM integration
6) Automated test troubleshooting
7) Advanced QTP Scripting
8) Expert View
9) Web applications
|4||Latest available version is IBM RFT v8.2||Latest available version is HP QTP v11.00|
|5||RFT uses Java scripts in addition to scripting with VB script.||QTP uses VBscript as the only scripting language.|
|6||RFT offers several data driven commands for creating various test cases. But the output values are manually keyed in.||QTP offers facility to parameterize our tests. Output values are automatically generated.|
|7||RFT supports frameworks like Keyword Driven, Data Driven & Modularity.||QTP supports frameworks like Keyword Driven, Data Driven, Library Architecture & Modularity.|
|8||RFT needs quite a bit of expertise compared to QTP.||QTP is quite easy to learn in a short time.|
|9||RFT does not support Descriptive Programming approach||QTP supports Descriptive Programming approach|
|10||RFT users need good experience of programming to achieve the objective.||QTP users can generate the script documentation automatically for every action performed in the keyword view.|
|11||RFT has its own default Reporting Formats as html. However for other interfaces we can do our own custom coding.||QTP offers Standard Reporting Formats like HTML, XML etc., while QTP has its own default UI and html.|
|12||RFT users don�t enjoy the Active Screen facility.||QTP comes powered with Active Screen facility that is greatly helpful in inserting the checkpoints|
|13||The output values are manually fed using the data pool feature of RFT.||QTP automatically generates the output values at runtime.|
|14||In RFT the object identification is quite good for standard objects. However identification of custom objects is tricky.||QTP scores an edge over RFT with its excellent object identification ability for all types of objects, including custom objects.|
|15||In RFT the user actions performed during recording are perfectly replayed during the playback. However selection of multiple values using the shift key is difficult.||QTP supports multiple value selection capabilities for playing-back the scripts.|
|16||Learning RFT needs a bit of expertise compared to QTP.||QTP being GUI based, is quite easy to learn in a short time.|
|17||Execution of test script is quite good in RFT.||QTP scores slight edge over RFT in this feature.|
|18||RFT users don�t enjoy such luxury as enjoyed by QTP users.||With QTP we can easily generate most comprehensive reports due to the availability of an efficient online help|
|19||RFT is licensed software & is less expensive compared to QTP.||QTP too is licensed software but its license cost is quite higher compared to RFT.|
The objective of this article had not been to favor one at the cost of the second. It is a matter of convenience for the testers & programmers to select a tool that suits their requirements best.
Lastly both these tools have their own advantages & shortcomings, while it all depends upon the users who truly knows how to exploit them to their best advantage.