plz tell me the drawbacks of selenium that in which case selenium fails,,means that it can't be applied.
selenium is open source automation tool , here you have to write your own code to develop your automation Suite. Selenium doesn't have an UI , here you have to integrate the components and many other things you have to consider while choosing Selenium for Automation.
In my perspective Selenium has more advantages over the drawbacks.
There's plenty of downsides..
* Support - There's no 1800 hot line. Support is mainly through the community on message boards, StackExchange, or on IRC. There is no committed support you can put support ticket to. Of course, you can just submit a problem in form of a bug, than someone gives you a nice solution while calling you an idiot at the same time.
* An advantage that's also a curse is Cross Browser support. Because Selenium is easy to run cross browsers on the grid, many will also find it a curse to support cross browsers. It's very hard to get a single script to truly work cross browsers. IE9 does not support CSS selectors as well as Chrome, Firefox's file upload blocks where IE10's doesn't. It's really a nightmarish experience to getting tests to work across platforms/browsers. With tools like QTP, Silk, Etc.. you end up just doing Windows Firefox latest, Windows Chrome latest, Windows IE latest. Then blame everything on the tool's in compatibility and call it mission accomplished. In Selenium, you start dealing with running tests on Windows/Mac/Linux/FreeBSD, browsers in Chrome, Firefox, IE10, IE9, IE8, PhantomJS. While each on it's own may not be that hard, getting a single test to run across them all so you can scale them on the grid is quite difficult.
* Open source also means you might find yourself contributing code to the project. If there's a bug with the tool, the company that hires me expects me to fix it if it's open source. With a proprietary off the shelf software, I can just blame it on the vender and put a ticket for them to fix it.
I still like Selenium despite it's drawbacks. It's one of the few solutions that's truly scalable. Imagine what it'll cost to run any per-seat licensed tool on the Cloud of 50 parallel instances. That's pretty common in most small shops that test cross browser/platform on selenium grid.
Very well written david...i strongly agree on the 5th point....that really puts us into a pathetic situation!
a 400 meter hurdle race:
1. Only web ( and now mobile) support
2. Unstable drivers for new browser release as unlike Selenium RC , Webdriver use similar browser concept so, one step behind the current trend.
3. If you stuck and don't have good face-linked-ing then start learning effective CVs or enjoy ( and probably test) office coffee machine in late evening. - Support.
4. If you are starter and end-up in traditional testing organization with no initial env of this open source. you may get High learning curve
Tags for this Thread