What is our primary use case?
We use it to make our UI functional tests, layout test, and any tests related to the browsers.
How has it helped my organization?
- We have automation tests (API, UI, unit, integration tests, and etc.). It saves on our manual QA time.
- It reduces our manual QA repeatable works.
- It saves our manual QA's energy.
- The QA time move from manual QA to automation QA, and improve the relationship between developer and QA, Since automation tests make them work closer.
- QA becomes more technical and love to know more about technical and architecture of the code such as they have to use GitHub, CI system, servers, and etc.
- QA know more about tests such as unit tests, integration tests, and Selenium UI tests.
- Make QA life much fun/easier.
- Deduce the developers work such as automation QA/developer develops the test library and test framework, both developer and QA, some times, PM also can develop their own tests by using the test library and test framework.
What is most valuable?
- Selenium is a good tool to do UI testing
- It supports most of the mainstream browsers such as Chrome, Firefox, IE and etc.
- It supports mobile local application as well and work with Appium.
- It is free.
- Selenium grid is a wonderful tool.
- BrowserStack and Sauce Labs work with Selenium.
- Headless browser, such as Xvfb and PhantomJS, can work with Selenium as well.
- Selenium works with CI system such as TeamCity, Jenkins, and CircleCI.
- Selenium can work with most programming languages. I use Java more as I am really comfortable using it.
- I do not use Selenium IDE, but it can help the beginner to learn how to find the elements by XPath, CSS selector, and etc.
- New geckodriver in new version of Selenium.
- It is able to work with Galen test framework to do layout test.
What needs improvement?
- Documentation, the Java doc description for most of the API is almost empty. No example with no detail.
- It is not easy to make IE plus Selenium work good as other browsers. Firefox and Chrome are the best ones to work with Selenium.
- Java gets a lot of supports. Python as well. However, it seems not PHP. It is amazing, and Selenium can work with a lot of programming languages.
- Firefox IDE tool needs to be improved.
What do I think about the stability of the solution?
Some times with timeout issues.
What do I think about the scalability of the solution?
When your tests number increases, driver manager and Selenium Grid performance become important.
How was the initial setup?
There are a lot of test frameworks that support Selenium.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Nov 09 2017