| Features | Watir | Selenium | QTP | WET |
| Support for most web objects | Yes | Yes | Yes | Yes |
| What you test is what you use? Does the test tool drive the application in exactly the same was as the end user? | Yes | No | Yes | Yes |
| Ability to identify objects using multiple parameters | No | No | Yes | Yes |
| Organizing tests similar to structured manual test plans | No | No | Good – By means of reusable actions / scenarios | Excellent Using test definitions |
| Ability to run multiple scripts consistantly in a Batch mode | No | No | No – Need Test director to be able achieve good results | Yes |
| Ability to store test application's objects so that scripts are well maintanable. | No | No | Good – But Quicktest's object repository mechanism is not always reliable | Excellent - uses the object depot which is very reliable |
| Easy creation of scripts | No | Record / Playback available via Selenium IDE | Yes Record / Playback | Yes Script / Assistant |
| Object Oriented Scripting Support | Excellent Uses Ruby | No | Good – But uses Vbscript which is not OO | Excellent - Uses Ruby |
| Integration with External libraries. | Very good – Uses the Ruby scripting language | No | Very good – Uses the vbscript scripting language | Excellent Uses Ruby and also has mechanism to allow libraries to be plugged in seamlesly |
| Reusability of Scripts and tests | Fair – Can write reusable classes / methods for library reusability but cannot directly reuse tests | No | Very Good 1) Can write Vbscript libraries and invoke COM dlls. 2) Can create reusable actions (aka reusable tests) | Excellent – 1) Has support for pluggin in libraries. 2) Reusable tests can be created 3) Every test can define preconditions / teardowns Uses Ruby and also has mechanism to allow libraries to be plugged in seamlesly |
| Reporting machanism | No | Excellent | Good – But requires a properietory tool to read results | Very good |
| Object parameterization | No | No | Yes | Yes |
| Integrated Data Driven Test framework support. | No | No | Yes | Yes |
| Popup handling support. | Poor | Good | Excellent | Good |
| Licensing | Opensource | Opensource | Commercial | Opensource |
| Keyword driven | No | No | Yes | No |
| Automatic Exception Handling | No | No | Yes | No |
| Learning curve | High – Requires tester to learn Ruby first | Good – Can use the Selenium IDE to get going. | Excellent- Can start using the record/playback to start learning QTP. QTP's documents are of high quality | Very good- Using the WET UI, one can start developing wet scripts quite easily |
| Commercial support | No | Good – Openqa offers Selenium hosting | Excellent- Mercury Interactive offers support and training. Training also available from 3rd parties | Excellent- Thwameva offers support and training |
| Interactive test debugging | No | Yes | Yes | No |
| Different Browser support | Only IE supported Firefox has barebones support | Excellent – Supports most browsers | IE and netscape supported Netscape has issues though | Only IE supported |
Selenium first came to life in 2004 when Jason Huggins was testing an internal application at ThoughtWorks.
Friday, 16 December 2011
Comparision of Web testing tools
Labels:
COMPARISION
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment