1. Home
  2. Automation Testing Tools
  3. Selenium Reviews
  4. User Review of Selenium
Selenium use and beyond
September 05, 2017

Selenium use and beyond

Shardul Negi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Selenium

Selenium basically is being used for automation of an internal website by one of our clients, Huawei. It is a good open source tool, and since it is open source, it has replaced the legacy automation (paid) for better results.
We have coupled the Selenium framework with REST and use the test cases to automate the 564 test cases for the application which have been integrated to CI.
Since Infosys caters to hundreds of clients, [use by] the whole organization would be an over estimation in my view, but it is catching on throughout the organization to automate repetitive flows.
  • It is open source.
  • Can be scripted in both Python and JAVA. I have recently started to code in Python and it reduces the complexity tremendously well.
  • It has a huge online open source community, so almost all the queries are answered.
  • I feel it is very slow.
  • The websites should follow certain standards for naming and easy processing of automation. There should be guidelines to code about naming and various other attributes of website development. It is difficult to go through or automate bad code with redundant tag names, bad formation and equally bad suggestions.
  • I think there should be Windows support. We can couple it with AutoIt, but by default, if [Windows support were available] it would be a huge help .
  • I feel Selenium solved the problem of CI integration and code refactoring issues.
  • It solved the problem of finding the loop holes and patches which had been amiss.
  • A framework should be made open source in market for website automation as well.
  • jubula, auto it and QTP
I feel Selenium has its limitations. But can not compare to any others.
Stable website automation. For Agile environments, REST and Selenium can be used together with a gap development of 1 sprint, i.e., using REST API validation for present deployment and then Selenium for measuring the UI components. So, the UI validation is 1 sprint before the whole process.