I have largely worked with Selenium for front end automation. Looks like there is great market for QTP in this arena, especially when you could afford commercial tools. Have you worked with both QTP and Selenium? How have your experiences been with both? Do you find any one better over other?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
closed as not constructive by Bruce McLeod♦, corsiKa♦, Dan Snell, Tarun, Edgar Gonzalez May 6 '11 at 21:51
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.
I have worked on both, and used QTP extensively before. It works best for teams that have one or two engineers who can create and maintain the test suites, and few more QAs with not so much programming skills can run the tests, and make minor changes. It's record and play (IMO) is better than selenium's.
Selenium is open source, so you are saving a lot of money that you would have to pay for licenses. Technologically Selenium surely goes way beyond QTP can, and due to the support for programming languages like JAVA, C#, Perl, Python, etc. the QA engineers can encompass backend tests too in their test suites.
Yes, selenium is better for web testing.
QTP is more expensive, and uses old technologies (VBA), but is better for non-coders and testing desktop applications
Now please, please, please close this question before the inevitable argument comes.