Please share with the community what you think needs improvement with Selenium HQ.
What are its weaknesses? What would you like to see changed in a future version?
I would like to see XPath made more reliable so that it can be used in all browsers.
The solution is an open-source tool. They should also build other features and tools to assist in further capabilities. A drawback of Selenium is that it only focuses on web applications. If it could be integrated into one application together with APM, it would be in peer competition with other players. Developers tend to bundle both in one, but Selenium is just in a silo. The solution's UI path needs to be modernized. The solution needs to offer a mobile platform.
The API that Selenium gives you doesn't act well with browsers. This should be improved. Right now, it's not stable.
The solution need to offer up much more information in regard to performance testing using selenium.
The solution should listen to the community and build new features for it based on their advice.
It does require a programming skill set. I would like the product not to require a heavy programming skill set and be more user-friendly for someone without a programming background.
Improvement in Selenium's ability to identify and wait for the page/element to load would be a big plus. This would ensure that our failed test cases will drop by 60%. Introduction of FluentWait has improved things, but it does not work in all scenarios