Genymotion vs. Selenium

When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.

Incentivized

• For any web based UI automation, Selenium is the best tool out there to automate your tests.
• It supports multiple coding languages like Java, Python, Ruby, C# etc.. to choose from.
• There is a huge community of users and can get many answers on StackOverFlow.
• It has lot of other plugins to make your tests even more efficient.

Incentivized

• Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
• Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
• Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.

Incentivized

We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.

Incentivized

As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.

Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.

Incentivized

We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.

Incentivized

At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.

Incentivized

• There hasn’t been a downside to using it yet other than we’ve got to update the programs we create for each change.
• This has saved us hundreds of hours of manpower by allowing our automation engineer to rapid fire tests.
• We are able to screenshot and save entire sites before and after launch with a program the automation engineer created
• We can compare large volumes of data against data in excel docs with a program created using Selenium

Incentivized